RE: Low-level math op behavior

2004-08-24 Thread Dan Sugalski
h. $i wouldn't get NaN if $i is an integer, though I expect everyone figured that one out. :) -Original Message- From: Dan Sugalski [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 24, 2004 11:29 AM To: [EMAIL PROTECTED] Subject: Low-level math op behavior Okay, since we're finally talki

RE: Low-level math op behavior

2004-08-24 Thread Butler, Gerald
: Tuesday, August 24, 2004 11:29 AM To: [EMAIL PROTECTED] Subject: Low-level math op behavior Okay, since we're finally talking defined math semantics, lets talk the low-level ops. All our math ops right now just quietly do their thing. If values wrap, truncate, or otherwise fuzz out, we don

Re: Low-level math op behavior

2004-08-24 Thread Doug McNutt
At 11:29 -0400 8/24/04, Dan Sugalski wrote: >What I'm thinking is that we add an O or X (or E, I don't care. I suppose we could >get more verbose there too) variant to the basic math ops which checks the result for >validity and throws an exception on something exceptional happening. For floatin

Low-level math op behavior

2004-08-24 Thread Dan Sugalski
Okay, since we're finally talking defined math semantics, lets talk the low-level ops. All our math ops right now just quietly do their thing. If values wrap, truncate, or otherwise fuzz out, we don't do anything special. This is fine, and fast, and what many languages want. It is, however, re