Re: File Naming Convention

Justin Patrin wrote:

On Mon, 06 Dec 2004 22:13:50 +0100, bertrand Gugger <bertrand@toggg.com> wrote:

Hi, ok, I'm talking too much too poor english. I agree totally on the file naming system. I'm just afraid as it can lead to some confusion: files with same name in different packages. e.g. (live) robert Peakes is proposing Net_Monitor I am proposing Console_Extend both of us work with HTTP so he gets: Net/Monitor/Service/HTTP.php and I get: Console/Extend/Remote/HTTP.php (I currently have the both of them here) OK, it's no problem, just a *could be dangerous* naming feature. Anyway, life is danger, regards.

This is what directories are for. The files are named this way for easy finding and access as well as easy loading. ok, Justin, I know what's a directory or folder (catalogue ?) is.

Just, I was in my lovely editor whith two tags HTTP.php and I thouhgt it could be dangerous... (I have big bloody fingers, they don't succeed all time on this keyboard). Where is the reason (apart history) to force such naming ? So far I can understand the "package.xml" file should describe the components. Could not the names be there ? Anyway, I agree that too long names are boring. Again, no aim to revolution, it's more to understand how it works. à+ -- bertrand