GNU bug report logs - #55635
`make-decoded-time' incorrectly sets DST to nil, it should be -1 (guess)

Previous Next

Full log

Message #28 received at 55635-done <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Maxim Nikulin <m.a.nikulin <at> gmail.com>
Cc: larsi <at> gnus.org, eggert <at> cs.ucla.edu, 55635-done <at> debbugs.gnu.org
Subject: Re: bug#55635: `make-decoded-time' incorrectly sets DST to nil,
 it should be -1 (guess)
Date: Sat, 28 May 2022 19:53:47 +0300

> Cc: 55635-done <at> debbugs.gnu.org
> From: Maxim Nikulin <m.a.nikulin <at> gmail.com>
> Date: Sat, 28 May 2022 23:31:43 +0700
> 
> I think, it is confusing that `make-decoded-time' is used to create 
> timestamps *and* time intervals. They are different types, for example 
> sum of intervals is meaningful (despite may be ambiguous) while there is 
> no point to add timestamps.

But this situation already exists with time units anyway.  You can add
an hour to some other time, but there's also a valid time stamp that
expresses 1 hour past the epoch UTC, and their values are exactly
identical.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.