James Mastros wrote:
> 
> Guys, can we please not argue over just how arithmetic
> and such works for NaN and Inf, and defer to IEEE specs
> (IEEE-754, AKA IEEE floating point)?  It'll save much
> argument, and that's how it'll almost certianly be
> implemented anyway.

NaN requires a pragma. As such, shouldn't documenting it be deferred till
later? And then, you might want to take a look at:

o  IEEE 754 Support in C99 document
   http://grouper.ieee.org/groups/754/meeting-materials/2001-07-18-c99.pdf

o  IEEE 754 web page
   http://grouper.ieee.org/groups/754/


> Give examples and references:

In chronological order:

Damian Conway:
> Perl NaN's will not be IEEE 754 compliant. 

Damian:
> NaN is dead.
[...]
> Except perhaps under a C<use IEEE> pragma of some kind, in
> which case it would be a proper IEEE Norweigian Blue NaN.

Larry:
>
> : IIRC, native data types, which are all lowercase (e.g.,
> : int, bit, long, etc.) cannot be undef. However, their
> : class equivalents (e.g., Int, Bit, Long, etc) can be undef.
> 
> That is correct.  It probably throws an exception if you
> try to assign an undefined value to a lowercase type.
> (Though an IEEE num might well set itself to NaN instead.)

So there you have it. NaN is outside the core... or at least a pragma
away...


Or pickup a thread:
http://www.mail-archive.com/perl6-language@perl.org/msg08521.html

http://www.mail-archive.com/perl6-language@perl.org/msg08359.html

http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&threadm=Pine.LNX.4.44.021
0311948500.18773-100000%40london.wall.org&rnum=1&prev=/groups%3Fnum%3D20%26h
l%3Den%26lr%3D%26ie%3DISO-8859-1%26q%3D%2B%2522IEEE%2522%2Bgroup%253Aperl.pe
rl6.language%2Bauthor%253ALarry%2Bauthor%253AWall





--
Garrett Goebel
IS Development Specialist

ScriptPro                   Direct: 913.403.5261
5828 Reeds Road               Main: 913.384.1008
Mission, KS 66202              Fax: 913.384.2180
www.scriptpro.com          [EMAIL PROTECTED]

Reply via email to