Peter Donald wrote:
> Because all the methods return this. In many cases this is considered a problem
> because it hides problems relating to;
>
> * synchronization
> * resource management etc.
>
> While those don't cover our situation I still consider
> it a bad practice because mutators/accessors should be
> sideeffect free IMO.
It is using the named parameter idiom:
* http://www.parashift.com/c++-faq-lite/ctors.html#faq-10.17
The code has no problems with synchronization or resource management because it is explicitly supposed to be used that way, and I think the use of the above idiom is justified in this case.
So please don't change it. (-1)
/LS
--
To unsubscribe, e-mail: <mailto:avalon-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@;jakarta.apache.org>
- Chaining Methods and Fortress Peter Donald
- Re: Chaining Methods and Fortress Leo Simons
- Re: Chaining Methods and Fortress Peter Donald
- RE: Chaining Methods and Fortress Berin Loritsch
- Re: Chaining Methods and Fortress Peter Donald
- Re: Chaining Methods and Fortress Peter Royal
- RE: Chaining Methods and Fortress Berin Loritsch
- Re: Chaining Methods and Fortress Leo Sutic
- Re: Chaining Methods and Fortress Peter Donald
- RE: Chaining Methods and Fortress Leo Sutic
- Re: Chaining Methods and Fortress Peter Donald
- Re: Chaining Methods and Fortress Peter Royal
- Re: Chaining Methods and Fort... Nicola Ken Barozzi
- RE: Chaining Methods and Fortress Berin Loritsch
