Re: pi seems not to be a constant

[email protected] (Don Cohen)
Newsgroups gmane.lisp.clisp.general
Message-ID <[email protected]>
 >     Don> It seems the best solution to this problem would be to
 >     Don> add to clisp the typespec (long-float precision) which would be a
 > I think that's not a valid float specifier.

Actually I now notice that (long-float 64) already is used to mean
long floats >=64
and (long-float 64 128) means those also <= 128.
I was thinking the implementation is allowed to extend these - is that
correct?  If so, I'd suggest (long-float 64 128 256) to mean a long
float between 64 and 128 having precision 256, and that type-of
return something like (long-float * * 256)
Or maybe (long-float 64 128 256 512) should mean a long float
between 64 and 128 with precision between 256 and 512 and type-of
should return (long-float * * 256 256)
(or it could return (long-float 99 99 256 256)

 > Is it conforming that cl:pi be a function?

I admit I've not paid enough attention to what things the
implementation is allowed to add to the standard.
If not cl:pi then perhaps ext:pi or some other name

 > And sorry to be pessimistic, but unless a maintainer steps up nothing
 > is going to happen. 
I recognize all that.
Someone does occasionally volunteer for this sort of duty.
The next person who works on MT or the next person who wants to really
make use of variable precision floats might want to do this.
Someone who wants to add variable precision to some other system might
also find this discussion useful.

------------------------------------------------------------------------------
_______________________________________________
clisp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-list
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.