On Tue, Jan 28, 2014 at 11:52 AM, Pierre Joye <[email protected]> wrote:
> On Tue, Jan 28, 2014 at 5:34 PM, Kristopher <[email protected]>
> wrote:
>
> > Really? I'd definitely love to see it for class and function names. Have
> you
> > ever tried to deploy or develop an application with a team on different
> > operating systems, and had the entire code puke because someone
> accidentally
> > did casing wrong on a class name and the autoloader barfed trying to load
> > the file on a case-sensitive operating system?
> >
> > I work with many developers using silly Mac OS X and it's case
> insensitive
> > file names. We deal with someone fat-fingering a class name on a regular
> > basis.
>
> We are not talking about file paths here but method, function, constant
> names.
>
>
Are we taking class and namespace names as well? Not sure why we would
address method, function and constant names and not address class and
namespace names.
And if we are addressing class names, then my point stands. When using
autoloaders, most often class and namespace names dictate path names.
So if we are talking class names, then we are most definitely talking paths
as well.