RE: [PEAR-DEV] "Namespace polution" in includes

Well the subdir issue could be solved by some redirect mechanism. Basically for anybody that updates their files would also grab this redirect mechanism. The mechanism could just be an include in the new correct path in the old location. So the transition would be easy but it would obviously introduce overhead to all old users that do not switch to include the file in the new path directly as they would call a require which would then do another require. Requires are quite expensive from what I have heard (of course DB connections are even more expensive) but its definitely overhead. If its noticeable will depend on your application (very likely if your app does not make use of any remote connections - like a DB call). All in all someone (the PEAR people) will have to weigh if they want to make life easy (actually with the redirect it would be easy since it would not require any changes but it would eat performance) on the existing user base or work to get rid if minor "uglynesses" to please new (potential) users like you. It seems that the current opinions do not seem to favour the latter. I guess both arguments are valid in the end it may just come down to the fact that you are outnumbered in this discussion, or that people hate to touch a running system ... Best regards, Lukas Smith smith@dybnet.de PS: somehow I keep moderating between the PEAR developers and "outsiders" :-) _______________________________ DybNet Internet Solutions GbR Alt Moabit 89 10559 Berlin Germany Tel. : +49 30 83 22 50 00 Fax : +49 30 83 22 50 07 www.dybnet.de info@dybnet.de _______________________________