Re: [Fwd: Re: PEAR framework changes for PHP5]

Hans Lellelid wrote:

I thought that PEAR classes generally included files according to how they are located in PEAR. E.g. Log looks for Log/drivername.php, MDB would look for a driver at MDB/drivername.php, etc. I'm aware that I could make my directory structure look like PEAR's and simply prioritize my classes in the include_path; I've seen other packages do this, but the point is that I don't think this should be necessary. I also dislike that all driver classes have to follow the namespace-style PEAR naming conventions (i.e. my Log driver class would have to be named Log_mydriver), but that is something I can live with until PHP has namespace support -- if ever :(

I dont really see this as an issue. If you dislike the current behaviour simply create your own custom behaviour. But I think its a valid assumption that people thats use PEAR are fine with the PEAR naming convention. Obviously I can make it possible to define your own custom class names, file locations etc. But this adds yet another feature which I dont see being used often. If you want the feature you simply add another factory or even modify the original factory (which reminds me .. it would be cool if the installer would detect modifications to files that are about to be changed by the installer in order to make it obvious to the user that he may have to port some custom mod). regards, Lukas Smith smith@backendmedia.com _______________________________ BackendMedia www.backendmedia.com berlin@backendmedia.com Linn Zwoch Smith GbR Pariser Str. 44 D-10707 Berlin Tel +49 30 83 22 50 00 Fax +49 30 83 22 50 07