Re: 0 SET-ORDER why?

On 29/06/2024 3:08 am, dxf wrote:

On 28/06/2024 11:48 pm, Ruvim wrote:

On 2024-06-28 16:19, dxf wrote:

On 28/06/2024 7:51 pm, Ruvim wrote:

...
If u is zero, the string must consist of zero digits.

>
Spec says:
>
    "u most significant digits of the significand"
>
Do you have a definition for '0 most significant digits of the significand' ?
I don't.  Nor did ANS provide one.

>
It's seems obvious to me: 0 digits means the empty string.

 
REPRESENT does two things:
- Round the number to produce another number
- Convert the resulting number to a string
 
u=0 fails on the first step as there's no such thing as a number rounded to
zero significant digits.  The resulting string is thus undefined.

Since posting the above I discovered the issue had been put to 200x with the
following response:

  "So with u=0 zero characters must be written to c-addr. Any implementation
   that writes something there is buggy. An exception for u=0 is also a bug
   (and in case of Gforth this bug will be fixed).

   There is no basis for any claim that the u=0 case is unclear or unspecified.
   And unsurprisingly, the person who claimed so presented no argument that
   would support such a claim."

Presumably that was a reference to me.  I consider the rationale I gave above
to be quite solid - unbreakable in fact.

It's good to know VFX' REPRESENT is "buggy" according to 200x.  I'll be keen
to see whether they fix it.