Re: [picocontainer-dev] renames ..
Mauro Talevi <[email protected]>
| Newsgroups | gmane.comp.java.picocontainer.devel |
|---|---|
| Message-ID | <[email protected]> |
Paul Hammant wrote:
> I really like the NLP style naming thats been introduced with Pico2.
>
> I'd like to take it a stage further .....
>
> CachingBehaviorFactory becomes Caching
> CachingBehavior becomes Cached
>
> ImplementationHidingBehaviorFactory becomes ImplementationHiding
> ImplementationHidingBehavior becomes HiddenImplementation
>
> PoolingBehaviorFactory becomes Pooling
> PoolingBehavior becomes Pooled
>
>
> etc.
>
> Rationale?
>
> All the BehaviorFactory implementations had the work 'ing' before
> BehaviorFactory.
>
> The simple 'ed' and 'ing' naming is quite purposeful, and may allow us
> to kill off the 'Behaviors' class
How so? Not clear how that would make a difference.
>
> Thoughts?
>
Don't really understand the rationale nor the benefits.
The risk once again is of becoming too cryptic in naming. If you have an interface X an impl YyyyX
is quite self-evident, while an impl Z is less so.
Cheers
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email