Re: [Chicken-users] utc-time->seconds and local-time->seconds rationale?

[Peter Bex]

On Tue, May 06, 2014 at 11:54:35PM +0200, Michele La Monaca wrote:
> On a side note, I've noticed these discrepancies on solaris, cygwin and mingw:
> 
> (use posix)
> (print (time->string (seconds->local-time) "%z")
>        " -> "
>        (vector-ref (seconds->local-time) 9))
> 
> +0200 -> -7200   (osx,     chicken 4.8.0)
> +0200 -> -7200   (linux,   chicken 4.8.0.3)
> +0200 -> -3600   (solaris, chicken 4.8.0.3)
> +0200 -> -3600   (cygwin,  chicken 4.8.0.3)
> +0200 -> -3600   (mingw,   chicken 4.8.0.4)

In my opinion, large parts of the POSIX unit should die.  They're broken,
at the wrong level of abstraction and just generally unschemely.  The
reason these time things are breaking is because the libc time access
is so varying across operating systems.

But even though they're so broken, people use it and rely on it, so
we can't simply put it out of its misery.

Cheers,
Peter
-- 
http://www.more-magic.net