* David Chelimsky [2011-12-07]:
> Nikolay - just because they're shareable doesn't mean they have to be
> shared :) As Pat suggests, you can use them to specify a subset of a
> single object's API. That said, one goal of thinking of roles is code
> that is easy to extend thanks to polymorphism. You
On Dec 7, 2011, at 4:07 AM, Pat Maddox wrote:
> On Dec 7, 2011, at 1:57 AM, Nikolay Sturm wrote:
>
>> * David Chelimsky [2011-12-07]:
reading "Growing Object-Oriented Software, guided by tests", I came
across the distinction of class, role and responsibility.
While classes ar
On Dec 7, 2011, at 1:57 AM, Nikolay Sturm wrote:
> * David Chelimsky [2011-12-07]:
>>> reading "Growing Object-Oriented Software, guided by tests", I came
>>> across the distinction of class, role and responsibility.
>>>
>>> While classes are classes and responsibilities could be mapped to public
* David Chelimsky [2011-12-07]:
> > reading "Growing Object-Oriented Software, guided by tests", I came
> > across the distinction of class, role and responsibility.
> >
> > While classes are classes and responsibilities could be mapped to public
> > methods, I wonder how to specify roles in my spe
On Dec 6, 2011, at 2:30 PM, Nikolay Sturm wrote:
> Hi,
>
> reading "Growing Object-Oriented Software, guided by tests", I came
> across the distinction of class, role and responsibility.
>
> While classes are classes and responsibilities could be mapped to public
> methods, I wonder how to speci
