Gnus development mailing list
 help / color / mirror / Atom feed
From: Hrvoje Niksic <hniksic@srce.hr>
Subject: Re: timezone.el patterns in emacs 19.34
Date: 03 May 1997 06:04:52 +0200	[thread overview]
Message-ID: <kigafmdmc9n.fsf@jagor.srce.hr> (raw)
In-Reply-To: Ken Raeburn's message of 02 May 1997 23:07:34 -0400

Ken Raeburn <raeburn@cygnus.com> writes:

> > it should be written in C.  It's not that hard to write, and the
> > speedup would measure by hundreds (all those regexps would become
> > unnecessary).
> 
> I'm not so sure about converting it to straight C; I could imagine
> wanting to change the supported format list someday, and wanting to do
> so easily -- i.e., without recompiling emacs.

I think it's a small price to pay for a big speedup of Summary buffer
building.  Emacs is not a particularly fast piece of software, and I
don't think we should miss things like this.  The speedup would be
enormous, really.

The extensibility is not lost, as this subr can be overridden with
whatever you like, including the old version.

> Besides, I think you'd probably wind up doing the regexp bit
> anyways, just at the C level.  These patterns don't have to match
> the *entire* string, just some substring.

I would do no regexp matching.  If I had to resort to regexps, then I
would rather leave it in Lisp, as it is.

> Now, if we can ignore or work around that substring issue (not a
> trivial issue, Gnus isn't the only user of that code), and require a
> match against the whole string, then using getdate.y might be a win.
> I understand it's supposed to be pretty comprehensive.

NO!  I hate getdate.y.  First, because of the `.y' thingie. :-)  Then,
there are copyright problems with it.  And, I'd like to have a fast
routine that matches those 7 or so format strings.  Nothing more,
nothing less.  If someone wants more -- the doors of Lisp are wide
open.  I opt for speed in this case.

-- 
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
Oh lord won't you buy me a color TV...


  reply	other threads:[~1997-05-03  4:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <199705020844.EAA06520@kr-laptop.cygnus.com>
1997-05-03  1:14 ` Hrvoje Niksic
1997-05-03  3:07   ` Ken Raeburn
1997-05-03  4:04     ` Hrvoje Niksic [this message]
1997-05-03 23:44       ` Ken Raeburn
1997-05-04  0:41         ` Hrvoje Niksic
1997-05-04  3:03           ` Ken Raeburn
1997-05-04 19:55             ` Hrvoje Niksic
1997-05-04 20:49               ` Johan Danielsson
1997-05-04 20:55                 ` Hrvoje Niksic
1997-05-04 22:22                   ` Public domain (was: timezone.el patterns in emacs 19.34) Johan Danielsson
1997-05-05  6:52                     ` Lars Magne Ingebrigtsen
1997-05-04 22:55                   ` timezone.el patterns in emacs 19.34 Stainless Steel Rat
1997-05-08 12:37         ` Lars Magne Ingebrigtsen
1997-05-03 22:41   ` Ken Raeburn
1997-05-02 23:18 Ken Raeburn

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=kigafmdmc9n.fsf@jagor.srce.hr \
    --to=hniksic@srce.hr \
    /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.
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 NNTP newsgroup(s).