Re: kick-off

Quoting David Sklar <sklar@student.net>: > That said, does it make sense to prefix all PEAR object names with something? > It's a lot more typing and might make the code uglier, but ensures that as > long as people don't write packages on their own that start with that prefix, > the packages won't step on each other. (i.e. the DB_mysql class gets called > "P_DB_mysql" or "PEAR_DB_mysql" or whatever..) I don't think this is worth the ugliness. You choose what packages from PEAR you use, so you _know_ what names will be taken up, so you can compensate for it. Personally, I plan to have Horde provide most of it's services as Pear packages, and I'll probably try and create a top-level Horde/ directory for all of them to go in, to avoid cluttering things terribly. If people stick to things like that, I don't think it'll be too big a problem. It'd be nice if you could do "use HTTP as MY_HTTP", and have the class dynamically renamed for you, but somehow I don't think we'll be seeing that. =) -chuck