On 20 Apr 2013 23:43, "Anton Kovalenko" <firstname.lastname@example.org> wrote:
> "Pascal J. Bourguignon" <email@example.com> writes:
> > Well with respect to compliance, AFAICR, there's nothing in the
> > Hyperspec saying that the precision of floating point numbers must be
> > constant during program execution.
> Except LONG-FLOAT-EPSION, that is documented to be constant but has to
> vary if the floating point precision varies. (That's what we see in
> CLISP: LONG-FLOAT-EPSION changes when you
Presumably the same holds for other fp constants as well (most-positive... etc)?
This is one of the reasons I wonder if it might be better to implement long floats as regular CMUCL-style 128 bit floats and variable/infinite precision as an extension using the potential number syntax. (Which would also be a neat opportunity to open NUMBER for subclassing, which in turn would open door for supporting units... but that is neither here or now, I guess.)