On 6 January 2014 14:21, Camille Teruel <camille.teruel@gmail.com> wrote:

On 6 janv. 2014, at 13:30, Alexandre Bergel <alexandre.bergel@me.com> wrote:

> You may need to do this if you are using proxies.

The fact that #== is not sent is actually really useful for proxies.
Because if #== were intercepted by the proxy and forwarded to the target then there is no straightforward way to make the distinction between two proxies on the same object.
And if messing with identity breaks all weak maps used for caching proxies.

right.. proxies are for obvious reasons quite closely related to identity problematics,

and in this regard, changing the #== gives more troubles than it solves,

because if you want to have a way to distinguish between proxy and non-proxy,
identity is a way to do it, but if there's no way to do identity comparison, then you broke :)

��

>
> Alexandre
>
>
> On Jan 6, 2014, at 8:52 AM, Igor Stasenko <siguctua@gmail.com> wrote:
>
>>
>>
>>
>> On 6 January 2014 10:56, Cl��ment Bera <bera.clement@gmail.com> wrote:
>> Hello,
>>
>> here I have a class
>>
>> A>>==
>> �� ^ true
>>
>> Now:
>> a := A new.
>> b := A new.
>> a == b "Answers false"
>> a perform: #== with: b "Answers true"
>>
>> Do I have to remove the usage of the byte code for #== in the compiler to be able to override == ?
>>
>>
>> may i ask why you need to override it?
>>
>>
>> --
>> Best regards,
>> Igor Stasenko.
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel ��http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>

--
Best regards,
Igor Stasenko.