From: Richard Stallman <rms@gnu.org>
To: Richard Lawrence <rwl@recursewithless.net>
Cc: emacs-devel@gnu.org
Subject: Re: Making decoded-times and calendar dates compatible?
Date: Tue, 10 Dec 2024 23:33:35 -0500 [thread overview]
Message-ID: <E1tLEPn-0000sh-M9@fencepost.gnu.org> (raw)
In-Reply-To: <87seqy5qr8.fsf@ohm.mail-host-address-is-not-set> (message from Richard Lawrence on Sun, 08 Dec 2024 13:00:11 +0100)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> If we changed them to use a format like, say,
> (YEAR MONTH DAY)
> and
> (YEAR MONTH DAY DOW HOUR MINUTE SECOND DST TZ)
> respectively, changing the relevant accessors, then calendar arithmetic
> functions could also work effortlessly with [the date part of] decoded
> times,
In principle it sounds like a good idea, but I think that the
incompatibility might be a big pain to fix. Doesn't some user code
have to operate on those formats?
I wonder also if calendar.el was designed to be compatible with
something in Unix that existed before GNU Emacs. But I wasn't the
one who wrote it, so I wouldn't know.
One possible way to make the incompatible change less of a pain to
cope with would be to use a list like
(calendar YEAR MONTH DAY)
in caledar.el. The presence of the synbol `calendar' would say "this
date uses the new format", thus avoiding ambiguity of the datum.
There would still need to be a lot of change, but at least it would be
easier to be sure you found all the places that had to be changed.
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
prev parent reply other threads:[~2024-12-11 4:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-08 12:00 Making decoded-times and calendar dates compatible? Richard Lawrence
2024-12-11 4:33 ` Richard Stallman [this message]
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=E1tLEPn-0000sh-M9@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rwl@recursewithless.net \
/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).