2009/7/8 Nicolas Cellier <[email protected]>: > 2009/7/8 Andres Valloud <[email protected]>: >> Well, but on the other hand, what happens when you do things like 1.0 + >> NaN or NaN + 1.0? It should work... >> > > Easy with double dispatching. > More boring is to coerce a (Float nan) created by a call to an > external library into a (Smalltalk at: #Nan). > I don't think so. The are few places where you need to change things, like in Interpreter>>floatObjectOf: aFloat to test against Nan, and return a NotANumber singleton instead of creating a new Float instance.
>> Igor Stasenko wrote: >>> 2009/7/8 Andres Valloud <[email protected]>: >>> >>>> Would NaN be polymorphic with floats? >>>> >>>> >>> Do you mean , be a part of Number/Float class hierarchy? >>> Answer is: no. >>> Because NotANumber is not a number :) >>> >>> -- >>> Best regards, >>> Igor Stasenko AKA sig. >>> >>> >> >> _______________________________________________ >> Pharo-project mailing list >> [email protected] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig. _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
