[SearchBuilder-devel] problems with capitalization.pm and OO modules

David Glasser glasser at bestpractical.com
Wed Jun 15 17:11:17 EDT 2005

On Jun 14, 2005, at 7:48 PM, Ruslan U. Zakirov wrote:

>> (c) Require every subclass of SearchBuilder to define the methods   
>> that
>> they override as CamelCase, and to also use capitalization to
>> lower_case all functions that they override.  But in this case:
>>    * capitalization is no longer the optional feature that we   
>> advertise
>> it as -- anybody who ever wants to make a subclass **must**   
>> follow this
>> rule
>>    * it requires subclassers to use CamelCase, which kind of defeats
>> the point of allowing customizable casing
> (d) Require every subclass put next code to the end of the package
> if( eval { require capitalization } ) {
>         capitalization->unimport( __PACKAGE__ );
> }

Yeah, but that still requires subclasses to use CamelCase *and*  
include that code. "We're going to have this cool feature that lets  
you use lower_case or CamelCase... unless you're making a subclass in  
which case there's no choice!" Not very much of a feature.

   Code Monkey, Best Practical Solutions
David Glasser | glasser at bestpractical.com

More information about the SearchBuilder-devel mailing list