Re: "Namespace polution" in includes

"Alexander Merz" <alexander.merz@s1999.tu-chemnitz.de> wrote in message news:001c01c19ff8$b36793a0$0200a8c0@alex... > > In my case, this "bug" is definetively a show-stopper... I'm not going to > > use PEAR if it can clash with my current or existing files... > It is a show stopper, if this problem occours, but not PEAR specific in any > way. With this opinion, you never could use any php scripts or applications > from other people. No. The difference here is that other people scripts are installed by hand one by one, instead of being included PHP by default. > PHP implements the include or require like other languages, the problem is > still a problem since programing languages supports more the one standard > include dir (>15 years) I completely agree with you on this. Just look at all the options in "configure" scripts for C programs (like PHP itself) But PEAR pretends to be the "standard library" (i.e. libc) in a language that doesn't has separate ways to include standard and non standard files (i.e. #include <...> vs. $include "..."). And to do so without having a simple way of distiguishing between the system files and your own is calling for trouble. As somebody else said on this thread, PHP 5 might be around the corner, but that doesn't mean everybody will stop using PHP 4 (or 3, for that matter). PEAR is currently migrating to a new directory structure (as in /pear/ instead of /php4/pear/)... why not do the change to a root "PEAR" directory right now?