From: Lute Kamstra <Lute.Kamstra.lists@xs4all.nl>
Cc: emacs-devel@gnu.org, ding@gnus.org, semi-gnus-ja@meadowy.org,
Miles Bader <miles@gnu.org>
Subject: Re: Changes in calendar/time-date.el
Date: Mon, 04 Apr 2005 12:57:32 +0200 [thread overview]
Message-ID: <87mzsezu5f.fsf@xs4all.nl> (raw)
In-Reply-To: <v9u0mm4z5c.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Mon, 04 Apr 2005 12:25:19 +0200")
Reiner Steib <reinersteib+gmane@imap.cc> writes:
>> I removed (require 'parse-time) from time-date because it uses just
>> parse-time-string, which is autoloaded. Do I understand correctly my
>> change uncovered some bugs in nnimap.el, nnultimate.el and pop3.el? I
>> already noticed (and fixed) this for message.el.
>
> Wouldn't it be better to put (require 'parse-time) at the beginning of
> the file instead of inside `message-make-date'?
message-make-date is the only function in message.el that uses
parse-time, so it's best to put the require there. If you change
message-make-date so that it no longer uses parse-time, you will
probably notice the require and remove it. Had you put require at the
beginning of the file, you would most likely forget this. Putting a
require at the beginning of a file is useful if the file uses a
particular feature a lot.
Lute.
next prev parent reply other threads:[~2005-04-04 10:57 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1DGYNu-00038g-00@quimby.gnus.org>
[not found] ` <yotly8c5jpi2.fsf@jpl.org>
2005-03-31 11:27 ` Changes in calendar/time-date.el (was: CVS update of gnus/lisp (4 files)) Reiner Steib
2005-03-31 12:20 ` Miles Bader
2005-03-31 12:58 ` Changes in calendar/time-date.el Lute Kamstra
2005-03-31 22:52 ` Miles Bader
2005-04-01 4:10 ` Richard Stallman
2005-04-04 10:25 ` Reiner Steib
2005-04-04 10:57 ` Lute Kamstra [this message]
2005-04-04 12:09 ` Reiner Steib
2005-04-04 12:52 ` Lute Kamstra
2005-04-04 17:20 ` Reiner Steib
2005-04-04 19:50 ` Stefan Monnier
2005-04-05 7:14 ` Kim F. Storm
2005-04-05 9:33 ` Miles Bader
2005-04-05 10:06 ` Kim F. Storm
2005-04-07 12:47 ` require inside functions. (was: Changes in calendar/time-date.el) Lute Kamstra
2005-04-07 21:45 ` Kim F. Storm
2005-04-08 0:12 ` require inside functions Miles Bader
2005-04-08 0:45 ` Stefan Monnier
2005-04-08 2:09 ` Miles Bader
2005-04-08 0:21 ` Stefan Monnier
2005-04-08 3:22 ` require inside functions. (was: Changes in calendar/time-date.el) Richard Stallman
2005-04-08 8:12 ` Kim F. Storm
2005-04-09 3:38 ` require inside functions. (was: Changes in Richard Stallman
2005-04-09 9:30 ` require inside functions Lute Kamstra
2005-04-10 1:55 ` Richard Stallman
2005-04-13 9:11 ` Lute Kamstra
2005-04-15 2:44 ` Richard Stallman
2005-04-15 9:23 ` Lute Kamstra
2005-04-08 8:16 ` David Kastrup
2005-04-05 13:54 ` Changes in calendar/time-date.el Lute Kamstra
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=87mzsezu5f.fsf@xs4all.nl \
--to=lute.kamstra.lists@xs4all.nl \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=miles@gnu.org \
--cc=semi-gnus-ja@meadowy.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.