2009/7/8 Igor Stasenko <siguctua@gmail.com>:
2009/7/8 Nicolas Cellier <nicolas.cellier.aka.nice@gmail.com>:
2009/7/8 Andres Valloud <avalloud@smalltalk.comcastbiz.net>:
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.
As I don't use VMMaker every day, last time it took me 3 hours to produce a VM (retrieving links, downloading, working around Monticello 1.5 initialization problem, and messing with directory structure and configure options). Just to apply an existing change... That's what I call boring :) But in theory, I agree, that should be easy. Nicolas
Igor Stasenko wrote:
2009/7/8 Andres Valloud <avalloud@smalltalk.comcastbiz.net>:
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 Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Best regards, Igor Stasenko AKA sig.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project