Re: [Scheme-reports] r7rs-draft-6: identifiers looking as numbers
Peter Bex
(10 May 2012 08:11 UTC)
|
[Scheme-reports] Date/time package
John Cowan
(10 May 2012 16:56 UTC)
|
Re: Date/time package
Arthur A. Gleckler
(10 May 2012 17:09 UTC)
|
Re: [Scheme-reports] Date/time package
Peter Bex
(10 May 2012 18:54 UTC)
|
Re: [Scheme-reports] Date/time package
John Cowan
(10 May 2012 21:07 UTC)
|
Re: [Scheme-reports] Date/time package
Peter Bex
(10 May 2012 21:58 UTC)
|
Re: [Scheme-reports] Date/time package
Alan Watson
(10 May 2012 22:07 UTC)
|
Re: [Scheme-reports] Date/time package
Noah Lavine
(10 May 2012 22:41 UTC)
|
Re: [Scheme-reports] Date/time package
John Cowan
(11 May 2012 02:43 UTC)
|
Re: [Scheme-reports] Date/time package
John Cowan
(11 May 2012 02:16 UTC)
|
Re: [Scheme-reports] Date/time package Peter Bex (11 May 2012 10:05 UTC)
|
Re: [Scheme-reports] Date/time package
Peter Bex
(11 May 2012 10:13 UTC)
|
Re: [Scheme-reports] Date/time package
John Cowan
(11 May 2012 14:35 UTC)
|
Re: [Scheme-reports] Date/time package
John J Foerch
(10 May 2012 23:40 UTC)
|
Re: [Scheme-reports] Date/time package
John Cowan
(11 May 2012 03:01 UTC)
|
Re: [Scheme-reports] Date/time package
John J Foerch
(11 May 2012 04:37 UTC)
|
Re: [Scheme-reports] Date/time package
John Cowan
(11 May 2012 04:44 UTC)
|
Re: [Scheme-reports] Date/time package
John J Foerch
(11 May 2012 05:25 UTC)
|
Re: [Scheme-reports] Date/time package
Daniel Villeneuve
(11 May 2012 03:35 UTC)
|
On Thu, May 10, 2012 at 05:07:05PM -0400, John Cowan wrote: > Peter Bex scripsit: > > > - The chronology stuff looks awkward to use. Especially the > > default-chronology is so ill-specified it's more or less useless. > > If it's supposed to represent the current machine time + zone, > > that makes sense but please say so, so that people can rely on that. > > If that remains unspecified, there's no portable way to obtain the > > user's current timezone. I noticed another problem. Since chronologies can hold any fields depending on the type, the default (or current-)chronology is still hard to use. If it's not iso-based, you can't fetch the hour from it for example. If you don't know what type it is, you can't really do anything with it. Maybe it makes sense to require that the default/current chronology is always an ISO type and if it's parameterized to something else, that's an error. Cheers, Peter -- http://sjamaan.ath.cx -- "The process of preparing programs for a digital computer is especially attractive, not only because it can be economically and scientifically rewarding, but also because it can be an aesthetic experience much like composing poetry or music." -- Donald Knuth _______________________________________________ Scheme-reports mailing list Scheme-reports@scheme-reports.org http://lists.scheme-reports.org/cgi-bin/mailman/listinfo/scheme-reports