bugGNU Common Lisp - Bugs: bug #50570, decode-universal-time daylight...

 
 

bug #50570: decode-universal-time daylight savings

Submitter:  None
Submitted:  Fri 17 Mar 2017 06:29:29 PM UTC
   
 
Category:  None Severity:  3 - Normal
Item Group:  None Status:  Fixed
Privacy:  Public Assigned to:  None
Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Tue 17 Jan 2023 10:59:16 AM UTC, comment #3: 

Greetings!  This is now fixed in 2.6.14.  Please be aware that there is one supported target, the original 2013 MinGW, on which the underlying localtime and mktime calls underpinning the implementation have a restricted range.


Camm Maguire <camm>
Group administrator
Wed 21 Dec 2022 02:29:14 PM UTC, comment #2: 

My apologies, closed in error.  Fix in progress.

Camm Maguire <camm>
Group administrator
Tue 21 Dec 2021 04:28:42 PM UTC, comment #1: 

Greetings!  Thanks for your report!

Camm Maguire <camm>
Group administrator
Fri 17 Mar 2017 06:29:29 PM UTC, original submission:  

With gcl 2.6.12 ANSI I get:

>(decode-universal-time 2414293200)


0
0
1
4
7
1976
6
T
4

while with cmucl and sbcl I get:
CL-USER(1): (decode-universal-time 2414293200)

0
0
1
4
7
1976
6
T
5

I am in the Eastern time zone and daylight savings time is
currently in effect.

CLHS says:
(When ``daylight savings time'' is separately represented as an argument or return value, the time zone that accompanies it does not depend on whether daylight savings time is in effect.)

GCl does not seem to be observing this, because it is adjusting the timezone from 5 to 4 while also representing d.s.t. separately.

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by camm (Posted a comment)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 6 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2023-01-17 camm StatusConfirmed Fixed
        Open/ClosedOpen Closed
    2022-12-21 camm StatusFixed Confirmed
        Open/ClosedClosed Open
    2021-12-21 camm StatusNone Fixed
        Open/ClosedOpen Closed

    Back to the top

    Powered by Savane 3.13-758e.
    Corresponding source code