[Vm-dev] failing/errors Pharo Tests with CogVM

K. K. Subramaniam kksubbu.ml at gmail.com
Fri Sep 17 00:28:17 UTC 2010

On Friday 17 Sep 2010 1:55:30 am Andreas Raab wrote:
> As a consequence we should never allow them to be introduced silently by 
> the VM. If the error handling code for some arithmetic primitive decides 
> that against all reasoning you'd like to produce an NaN as the result 
> regardless, that's fine, you have been warned. But having the VM 
> introduce NaNs silently is wrong, wrong, wrong.
What are the implications of mapping nil <-> NaN at the Object <-> IEEE number 
boundary? i.e. Both NaN and nil will evaluate as NaN in numeric contexts and 
nil in other contexts.


More information about the Vm-dev mailing list