Re: Re: PEAR2 Coding standards, Autoloading and Namespaces

Hi Jeff, I'm not going to take a jab at this NS thing but rather at a point that couple of people have raised On Sat, Apr 5, 2008 at 4:53 PM, Jeff Moore <jeff@procata.com> wrote: > Pro: > * External code can use a short and natural reference [PEAR2::Foo] to > refer to the Foo class. > > Con: > * Foo.php is not in the Foo directory (confusing, bad for version control) This comment makes it seem like you've ever never never used a version control system ... really ... no offense but it does sound that way. Have you never thought about it like this: repo - pear -- File (this is the repo dir) --- File.php ---- File (a dir) ----- CSV.php (class File_CSV) ----- Util.php (class File_Util) This is a real world example: http://cvs.php.net/viewvc.cgi/pear/File/ Not sure how you think it's confusing and not working for a VC ... sure it's confusing if you tend to look at your PEAR installation dir, doubt many people will that don't have the capacity to understand the internals of PEAR will ever venture in there at any real rate, it's like trying to make the registry db of windows understandable for my mom ... not going to happen ;-) I can see the point of having File.php inside the File dir on installations, I've nothing against that but it would have to be: - pear-root -- File --- File.php --- File ---- CSV.php ---- Util.php Or at least that's how I understand it ... comes kinda confusing as well ... doesn't ? Users see a file dir, click it, hey another file dir but I just clicked it ... *head explodes* Anyway I just wanted to comment on that single bit. - Helgi