[prev in list] [next in list] [prev in thread] [next in thread] 

List:       groovy-user
Subject:    Re: [groovy-user] Re: Inconsistent categories behaviour to override ==
From:       Carlos Sierra Andrés <csierra () gmail ! com>
Date:       2013-04-26 14:43:14
Message-ID: 517A9282.9030605 () gmail ! com
[Download RAW message or body]

Hi again,

thanks for the replies... What I would also be interested in knowing is 
which is the expected correct behaviour. I mean, whether it is expected 
to be able to override == using categories.

Bests.

El 26/04/13 14:18, Andre Steingress escribió:
> Hi,
> 
> It seems the technical reason is
> DefaultTypeTransformation#compareEqual(Object, Object) is directly calling
> DefaultGroovyMethods#equals(List, List).
> 
> The Maps call is delegated to InvokerHelper which causes your equals method
> to be invoked (otherwise it would delegate to
> DefaultGroovyMethods#equals(Map, Map)).
> 
> Maybe someone can bring in some light on the behaviour of
> DefaultTypeTransformation (and a possible workaround).
> 
> Cheers, André
> 
> 
> 
> --
> View this message in context: \
> http://groovy.329449.n5.nabble.com/Inconsistent-categories-behaviour-to-override-tp5715188p5715191.html
>  Sent from the groovy - user mailing list archive at Nabble.com.
> 
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
> 
> http://xircles.codehaus.org/manage_email
> 
> 


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


[prev in list] [next in list] [prev in thread] [next in thread]