On Thu, Sep 11, 2008 at 6:49 AM, Rick McGuire <[EMAIL PROTECTED]> wrote:
> ... There are > basically two issues. 1) How to deal with values getting passed out as > arguments and 2) Dealing with the edge cases of values getting passed back > in. > > ... There's no checking for the infinities at this > boundary, so the infinities will get passed as arguments in the float case. > Easy enough to add a check so this is consistent, but this begs the question > of whether we might actually want to allow the infinity values to get passed > through. My gut instinct is no, and it's generally easier to lift an > restriction than to impose one at a later time, so it can't hurt to keep > this an error. An error is also consistent with how integer value arguments > are handled. Well, I think no also, giving weight to the is consistent with how integer values are handled. > ... I fixed this in the > infrastructure by having a nan value map to the character string "nan". I > can do the same for "+infinity" and "-infinity" in the infrastructure if we > agree that's the desired behavior. Right now, it appears that at least for > the float tests, a returned infinity is getting formatted as a "1", which is > definitely not a correct result. Mapping nan, +infinity, and -infinity to string names seems reasonable to me. -- Mark Miesfeld ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
