On Mon, May 14, 2012 at 10:19 PM, Martin Dias <[email protected]> wrote:
> Hi all > > I have some methods receiving either a Class or a Trait instance as > parameter, so I usually call variables with names like > 'aClassOrTrait'. Searching for a more synthetic name, I wonder if > 'aBehavior' would be fine. > +1. For all my code that can handle both, traits and classes, I ALWAYS use the word Behavior rather than class. Problem is that aTrait isBehavior -> false. But I think it is an implementative details and I don't like it. As you say, a trait for me is a behevior and therefore I use that word. > > But IMO these examples show contradictions: > > - Trait *is* a behavior: > > TBehaviorCategorization users ---> an IdentitySet(Class Trait) > > TPureBehavior users ---> an IdentitySet(TraitBehavior Behavior) > (actually this makes me think 'aPureBehavior' is another alternative > for my variables) > > - Trait is *not* a behavior: > > TBehaviorCategorization isBehavior ---> false > > TClassAndTraitDescription users ---> an IdentitySet(ClassDescription > TraitDescription) > (I both are behaviors, why not call it TBehaviorDescription?) > > > Thanks in advance for your help. > MartÃn > > -- Mariano http://marianopeck.wordpress.com
