From: Lars Ingebrigtsen <larsi@gnus.org>
To: Andreas Politz <politza@hochschule-trier.de>
Cc: 14776@debbugs.gnu.org
Subject: bug#14776: 24.3.50; [PATCH] parse-time-string performance
Date: Tue, 01 Mar 2016 12:05:34 +1100 [thread overview]
Message-ID: <87k2ln3t41.fsf@gnus.org> (raw)
In-Reply-To: <m3ehb9f6lc.fsf@stories.gnus.org> (Lars Magne Ingebrigtsen's message of "Mon, 08 Jul 2013 16:51:11 +0200")
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>> Anyway here is an updated version, incorporating 2-digit years and
>> textual timezones.
>
> Looks good.
I did some further tests (after the version of parse-time-string on the
Emacs trunk had been ... fixed), and the regexp version is still 3x
faster (down from 10x).
It is, though, a stricter RFC2822 parser than the version we currently
have, so it fails on some of the test cases (dates without times, for
instance). So I'm still not sure whether this is a suitable replacement
for parse-time-string. And it seems odd to have two completely
different functions that almost parse the same thing...
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2016-03-01 1:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 1:21 bug#14776: 24.3.50; [PATCH] parse-time-string performance Andreas Politz
2013-07-03 1:27 ` Andreas Politz
2013-07-03 3:32 ` Glenn Morris
2013-07-03 3:34 ` Glenn Morris
2013-07-04 15:41 ` Andreas Politz
2013-07-04 18:41 ` Lars Magne Ingebrigtsen
2013-07-04 19:47 ` Andreas Politz
2013-07-04 20:31 ` Lars Magne Ingebrigtsen
2013-07-04 21:08 ` Andreas Politz
2013-07-04 21:15 ` Lars Magne Ingebrigtsen
[not found] ` <87hagaeztj.fsf@hochschule-trier.de>
2013-07-06 15:34 ` Lars Ingebrigtsen
2013-07-06 15:50 ` Andreas Politz
2013-07-06 15:56 ` Lars Ingebrigtsen
2013-07-06 16:07 ` Andreas Politz
2013-07-06 17:47 ` Andreas Politz
2013-07-08 14:51 ` Lars Magne Ingebrigtsen
2016-03-01 1:05 ` Lars Ingebrigtsen [this message]
2019-06-27 11:12 ` Lars Ingebrigtsen
2013-07-04 22:21 ` Andreas Politz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k2ln3t41.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=14776@debbugs.gnu.org \
--cc=politza@hochschule-trier.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).