From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Lute Kamstra <Lute.Kamstra.lists@xs4all.nl>,
Miles Bader <miles@gnu.org>,
ding@gnus.org, emacs-devel@gnu.org
Subject: Re: Changes in calendar/time-date.el
Date: Mon, 04 Apr 2005 15:50:05 -0400 [thread overview]
Message-ID: <jwvvf72ba2e.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <v94qembgqs.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Mon, 04 Apr 2005 19:20:59 +0200")
>>> (eval-when-compile
>>> (require 'cl)
>>> (defvar parse-time-weekdays) ;; parse-time is required where necessary
>>> (defvar parse-time-months)
Why not (require 'parse-time) simply?
This way if parse-time is ever changed to remove parse-time-months, the
byte-compiler will correctly catch it.
> `with-no-warnings' isn't available in Emacs 21.
with-no-warnings should be avoided as much as possible since it can hide any
warning whatsoever without justification. (defvar foo) explains to the
byte-compiler (and the human reader) *why* the warning should be skipped.
> (defun nnimap-date-days-ago (daysago)
> "Return date, in format \"3-Aug-1998\", for DAYSAGO days ago."
> + (require 'parse-time)
> + (defvar parse-time-months)
A (defvar foo) form only makes sense at the toplevel.
Stefan
next prev parent reply other threads:[~2005-04-04 19:50 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
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 [this message]
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
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=jwvvf72ba2e.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=Lute.Kamstra.lists@xs4all.nl \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=miles@gnu.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 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).