Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> wrote:
> >
> > # define Parrot_is_nzero(x) ((x) == copysign(0.0, -1.0))
use that if signbit isn't, patch? applied ;)
Thanks,
leo
> PS -- Brent my ISP seems to be having an argument with perl.org at the
> moment, if this does not make it to the list will you forward it along
> for me? Thanks.
As requested. I may have mis-threaded this--sorry if I did.
> All~
>
> I just discovered that my system does have copysign so the fo
Mitchell N Charity <[EMAIL PROTECTED]> wrote:
> to
> if (value == vali && (0 != vali || ...something...))
> perl 5.9.0 devotes several configuration arguments to finding a
> floating point classifier (fpclass or similar). And 100+ lines of
> perl.h to using them. Defines quite a few macr
On Tue, Mar 16, 2004 at 08:13:06PM +0100, Leopold Toetsch wrote:
: Mitchell N Charity <[EMAIL PROTECTED]> wrote:
:
: > if (value == vali && (0 != vali || ...something...))
:
: Yep here it is.
:
: Do we *really* need that crap?
That depends on who "we" are, unfortunately.
Larry
Mitchell N Charity <[EMAIL PROTECTED]> wrote:
> if (value == vali && (0 != vali || ...something...))
Yep here it is.
Do we *really* need that crap?
> Mitchell
leo
> PerlNum may not be handling -0.0 correctly.
I do consider -0.0 as a bug ;)
;)
However, distinguishing 0.0 from -0.0 is floating point standard.
And thus needed for interoperating with standards-following systems.
Such as perl. (And ruby and python.)
Windows apparently has issues (witnes
Mitchell N Charity <[EMAIL PROTECTED]> wrote:
> PerlNum may not be handling -0.0 correctly.
I do consider -0.0 as a bug ;)
> This
> new P0, .PerlNum
> set P0, 0.0
Both setting P0 to - or + zero has the same effect:
$ parrot -t 0.pasm
0 new P0, 35 - P0=NULL,
3 set P0, 0
PerlNum may not be handling -0.0 correctly.
This
new P0, .PerlNum
set P0, 0.0
print P0
print "\n"
set P0, -0.0
print P0
print "\n"
end
prints this
0
0
rather than say this
0
-0
For reference,
perl -e 'print -0.0,"\n"'
prints
-0
Thanks to ruby's test suite for the catc
