Re: [Chicken-users] Exact flownums not properly displayed in mingw

[Jim Ursetto]

Heh.  That is pretty amusing, but more a formatting issue on the part of 
chicken-status.  Or you could chalk it up to the egg's use of a flonum instead 
of a string or symbolic version number (0.2.3 is read as a symbol, whereas 0.2 
is read as a number).  For example, were you to use (version 1.00), it would 
read as a flonum and display "1.0" on UNIX, which is just as incorrect as "1." 
in my opinion.

One way to quickly fix this for your case is to change (version 1.0) to 
(version "1.0") in your .setup file.  I try to use string version numbers 
exclusively now for consistency's sake.

Jim

On Jul 9, 2013, at 12:12 PM, Michele La Monaca <address@hidden> wrote:

> On Tue, Jul 9, 2013 at 6:31 PM, Jim Ursetto <address@hidden> wrote:
>> If you're really concerned about this (which is ultimately aesthetic)
> 
> Is this acceptable?
> 
> C:\TMP>chicken-status | tail -3
> socket ....................................................... version: 0.2.3
> srfi-37 ...................................................... version: 1.3.1
> win32-msgbox .................................................... version: 1.
> 
>> then you should consider setting flonum-print-precision to 17, which will
>> make an actual difference in rare
>> cases.  http://api.call-cc.org/doc/library/flonum-print-precision
> 
> It doesn't seem to do any difference (in this case at least). Thanks, anyway.
> 
> Michele