On Wed, Aug 22, 2012 at 8:26 AM, Mike Cowlishaw <m...@speleotrove.com> wrote:
Treating .nil like NaN is an interesting model. Worth thinking through, I'd
suggest (including .nil \= .nil) ...
Not a good idea on this last one...this feature request exists because of some
unexpected side effects of "if a = .nil" comparisons. Always having .nil never
be equal to itself would break a lot of programs!
Have to take your word for it on that .. but it may be the only way to have a
consistent 'story', rather than special cases scattered throughout multiple
classes. That's [partly why] NaN \= NaN came to be; it was the only closed
system that worked.
But yes, needs of existing programs are paramount.
Mike
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
