Re: encode-universal-time bug (maybe not?)

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--0-2132815081-1144999948=:8925
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN; format=flowed
Content-Transfer-Encoding: QUOTED-PRINTABLE

Thanks; I think that this is a bug.  CLHS 25.1.4.1 (Decoded Time) would
seem to apply here, and whatever it's doing with the year "3" doesn't
seem to be what that section refers to as the "obvious" interpretation.

On Fri, 14 Apr 2006, [utf-8] Lu=C3=ADs Oliveira wrote:

> Hello,
>
> I'm not sure if this is an actual bug. The spec doesn't say much about
> it but openmcl's behaviour differents from every other lisp:
>
> pomajxego:~ luis$ openmcl
> Welcome to OpenMCL Version 1.0-p060223 (DarwinPPC32)!
> ? (encode-universal-time 0 0 0 1 1 3 0)
> -59863449600
> ? (encode-universal-time 0 0 0 1 1 2003 0)
> 3250368000
>
>
> All other lisps return the same value for both calls. Ie, they interpret
> 3 as 2003.
>
> --=20
> Lu=C3=ADs Oliveira
> luismbo (@) gmail (.) com
> Equipa Portuguesa do Translation Project
> http://www.iro.umontreal.ca/translation/registry.cgi?team=3Dpt
>
> _______________________________________________
> Bug-openmcl mailing list
> [email protected]
> http://clozure.com/mailman/listinfo/bug-openmcl
>
>
--0-2132815081-1144999948=:8925
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Bug-openmcl mailing list
[email protected]
http://clozure.com/mailman/listinfo/bug-openmcl

--0-2132815081-1144999948=:8925--