Krishna Myneni <krishnamyneni@[EMAIL PROTECTED]
> writes Re: >FLOAT behavior
with null string
> The specification of >FLOAT in DPANS94 suggests that it treat a string
> of blanks as a representation of zero (below). Common practice among
> Forth systems (pfe, gforth, bigforth) appears to extend this suggested
> behavior to null strings as well, e.g.
> s" " >FLOAT
> returns a true flag on the stack, and fp zero on the floating point
> stack. Is there a strong argument for considering a null string to be a
> valid representation of fp zero.
I guess that when reading a table, empty fields (all blanks) should parse
as zero.
This means that the last column(s) on a line is (are) a problem when
someone has removed trailing spaces (humans would still know what is
being intended).
Or even easier (comma-delimited list):
1.13,3,,888,,,7e12
But I could be wrong.
-marcel
|
