Re: Re: PEAR2 Coding standards, Autoloading and Namespaces

> I keep running into it. Where I'm working now, they use svn:externals for > several things. For PEAR, they check in the install directory to use it > like an svn:external. (I say they instead of we because this was setup > before I got there.) I can tell you the depth of the directory tree in this > setup is extremely annoying. > > Consider that the current directory structure for > http://cvs.php.net/viewvc.cgi/pear/File in subversion requires > two File > folders. The alternative that I am describing uses only one I must admit I could see the merit of having it in the same folder, but with your idea would PEAR2::File::CSV::Foo be in the same dir as CSV or in File/CSV/Foo.php ? I'd presume so in this case since we've gone one level down in the hierarchy but I'd like to see how you think of the problem. Also say PEAR2::File::CSV:: Bar (or the lowercase, which ever way we go) is in a completely new package, say someone outside the File package wanted to add something new ... Basically a PEAR2_File_CSV_Bar package, which until now has been competly okey (See MDB2 drivers for example) ... Where would that be installed ? Along side Foo.php in the installation dir or somewhere else ? I'm mostly looking for how you see this before taking this part of the discussion any further, so that we don't have any unnecessary misunderstanding :-) Regards Helgi