On 2 May 2013 17:40, Guillermo Polito <guillermopolito@gmail.com> wrote:

#bindedXXX and #boundXXX sounds pretty static to me... It's like it was already binded. And maybe in the back it is dynamically looked up. Maybe a more abstract name can fit better:

#resolveToClass ? #lookupClass ?

Also (I'm pretty negative today), let's do not forget about traits! (We always do, and that gives us problems later )

That reminds me: I found a bug when aliasing binary selectors in Traits. Until today Squeak's Associations printed without whitespace around the ->, so in a trait like Object subclass: MyObject uses: TMyTrait @ {#* -> #+} the Browser would print the TraitComposition as "TMyTrait @ {#*->#+}". (This isn't valid Smalltalk: it's the Symbol #*-> followed by garbage.} I'm not sure what the situation is in Pharo (I'm not in a position to check it right now), but it's worth a look. frank

On Thu, May 2, 2013 at 6:33 PM, Chris Cunningham <cunningham.cb@gmail.com> wrote:

...

On Thu, May 2, 2013 at 9:29 AM, Esteban Lorenzano <estebanlm@gmail.com> wrote:

...

#bindedClass #bindedClassOn: anEnvironment

looks clearer to me.

Esteban

maybe: #boundClass #boundClassOn: anEnvironment