Re: Re: PEAR2 Coding standards, Autoloading and Namespaces

Hello Jeff, > 2.) Mapping package names to namespaces. I suggested this because > it was possible, and to find out what people thought of it. If its a > bad idea, then thats that. I have no strong feelings on this point > and as it might conflict with #1, I favor that naming convention over > this one. I'd like to think outside the box, if you could tell me the solution for following problem: - Package MDB3 - Driver packages MDB3_Sqlite, MDB3_MySql etc How do you load those drivers? Currently it was as easy as checking the existence of $path/MDB2/Driver/Sqlite.php and include the file with that name. If every package uses his own namespace, how do you load such a driver? Where do you store it in the file system so that it can be easily found? Making exceptions to the packagename->namespace rule would work, but defeat the purpose of the whole idea. -- Regards/Mit freundlichen Grüßen Christian Weiske

Attachment: [application/pgp-signature] signature.asc