Ah, sorry, I'd overlooked the subject line so I didn't realize you were talking about value proxies. I haven't digested the design space for value proxies, so I don't have anything to say about this yet. (Value proxies will not be in ES.next; they're still in a fairly early stage of design.)
Dave On Apr 17, 2011, at 8:55 AM, Adam Stankiewicz wrote: > By overwriting I meant creating a trap for === operator. Sorry for confusion. > > Adam > > 2011/4/17 David Herman <dher...@mozilla.com>: >> I don't understand. What is "overwriting" an operator? >> >> Dave >> >> On Apr 17, 2011, at 7:52 AM, Adam Stankiewicz wrote: >> >>> Hello everyone, >>> >>> My idea is to disallow overwriting of === operator, and make 'compare' >>> operator implement == instead. Why? >>> >>> 1. === means for me that two variables have reference to the same >>> object, so there is no point of overwriting it. Many programmers would >>> be confused. >>> 2. == always caused problems, above change gives it opportunity to >>> return to grace. >>> >>> You don't know if they are the same object? Use ===. Don't know if >>> these objects are the same, but only in eyes of programmer? Use ==. >>> Think about == or < as semantical operators, and === as hard-cored >>> is-the-same-object function. >>> >>> Overwriting === operator would also probably cause problems in >>> security (membrane design etc.), but it is only my guess. >>> _______________________________________________ >>> es-discuss mailing list >>> es-discuss@mozilla.org >>> https://mail.mozilla.org/listinfo/es-discuss >> >> _______________________________________________ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
