Re: pi seems not to be a constant

Pascal J. Bourguignon wrote:
  > But this argument is the one that requires us to fill RAM with that
  > one best approximation.
  > Clearly we have to give up compliance on the point of pi being the
  > best approximation the implementation can provide.
  Not necessarily. I gave you a way to do it without losing compliance.

What way was that, other than filling RAM ?

  > - I want pi and the other similar constants to be defconstant
  >    keeping their initial values.

  Then you need an abstract value ext:pi (?) that provides a different
  precision depending on *long-float-digits*

I don't know what you mean here by "an abstract value".
I also don't see why you want a symbol bound to a value 
(that has to be recomputed eagerly?) rather than a function.

  It's not a symbol macro, because:
    (defconstant cl:pi #S(ext:=CF=80))
    cl:pi --> #S(ext:=CF=80)
    (+ 0 cl:pi) --> 3.141592l0

I also don't yet understand either what's wrong with anything in the
example above or why ext:pi can't be a symbol macro.
Nor do I yet understand why you seem to be concerned with contolling
how these things print.



------------------------------------------------------------------------------
_______________________________________________
clisp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-list