On Thu, 25 Mar 2010 02:50:41 -0400 Alexander Belopolsky firstname.lastname@example.org wrote:
Bertrand Meyer again:
""" A few of us who had to examine the issue recently think that — whatever the standard says at the machine level — a programming language should support the venerable properties that equality is reflexive and that assignment yields equality. """
IEEE standards were developed in a different problem domain: hardware or low level programming language design. They may not be appropriate for an object oriented language like Python. Java and recently Eiffel designers seem to have realized that.
Hum, should the above be interpreted as: a = NAN ==> not only a is NAN but also a == NAN
and further: b = a ==> b == a
? (Else there should be a distinction between equality assignment and identity assignemt? b = a # ==> a is b and a == b b := a # ==> a is b and possibly a == b ;-)
vit esse estrany ☣