floating point and other comments
Alex Shinn
(18 Dec 2003 02:58 UTC)
|
Re: floating point and other comments
Ken Dickey
(18 Dec 2003 16:17 UTC)
|
Re: floating point and other comments
Alex Shinn
(19 Dec 2003 01:55 UTC)
|
Re: floating point and other comments
Ken Dickey
(20 Dec 2003 02:34 UTC)
|
Re: floating point and other comments
Alex Shinn
(20 Dec 2003 08:56 UTC)
|
Re: floating point and other comments bear (20 Dec 2003 19:00 UTC)
|
Re: floating point and other comments
Alex Shinn
(22 Dec 2003 02:16 UTC)
|
Re: floating point and other comments
bear
(23 Dec 2003 02:01 UTC)
|
Re: floating point and other comments
Alex Shinn
(23 Dec 2003 04:38 UTC)
|
Re: floating point and other comments
Ken Dickey
(22 Dec 2003 02:56 UTC)
|
Re: floating point and other comments
Per Bothner
(20 Dec 2003 18:05 UTC)
|
Re: floating point and other comments
Ken Dickey
(22 Dec 2003 00:41 UTC)
|
Re: floating point and other comments
Alex Shinn
(22 Dec 2003 03:50 UTC)
|
Re: floating point and other comments
Ken Dickey
(22 Dec 2003 17:05 UTC)
|
Re: floating point and other comments
Alex Shinn
(23 Dec 2003 05:23 UTC)
|
Re: floating point and other comments
Alex Shinn
(23 Dec 2003 05:26 UTC)
|
On Sat, 20 Dec 2003, Alex Shinn wrote: >On Fri, Dec 19, 2003 at 06:13:27PM +0100, Ken Dickey wrote: > >> I will be happy to work with you on an "advanced format" spec which >> includes this if you would like. > >OK, but my personal format just took a turn for the weird and there >are some issues I want to work out first. And if we ever want to get >"complete CL format" we'll need a circular-write SRFI and a >pretty-print SRFI. We've already got a circular-write SRFI (srfi-38). As far as I know there aren't implementations without prettyprint in some form, but there's no SRFI for it. >Also, the spec says it is an error to pass fewer arguments than >needed, but is it ok to pass more arguments? Interesting question. I would say that it should be but only if there is a "null conversion" available - Something that eats an argument without producing output. The rationale is use for internationalization, where there's rarely a 1-to-1 or identically- ordered correspondence between different languages. Bear