Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:60243
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAKOpQSxbmcn2wxLuUMOpLd0NbNL==dV3cm4rhWmW_rNsjukNFw@mail.gmail.com>
References: <jmrdbg$bh4$1@dough.gmane.org>
	<CAF+90c8NxUvXOEbFbN=U6QBNqvHLsa9Jfgx_1fpWss5ASCX11Q@mail.gmail.com>
	<CAL0xaBGfw35FPFTs=CZwc4OLDzB9N6N2uHdQsi8vmagmB-qVXA@mail.gmail.com>
	<CAL+t6cGM7gBWsiPYn8EbTEZm=OBb1=vrWzbyURRTgCvvKOUwLg@mail.gmail.com>
	<CAL+t6cECGQHJyxKew=U5t_wJV=8fKf6X-UaiwiEChy2=UE0=uw@mail.gmail.com>
	<CAGsnKxanO0oraHHB=+v61=-y7WtQR5vbN1fxHHzcagjFncmveg@mail.gmail.com>
	<CAL+t6cGksdaPJUanXxRcV25dNz2bPXd72SZJ-Yjs0M9ni28Nyw@mail.gmail.com>
	<CAKOpQSxbmcn2wxLuUMOpLd0NbNL==dV3cm4rhWmW_rNsjukNFw@mail.gmail.com>
Date: Fri, 20 Apr 2012 14:47:38 -0400
Message-ID: <CAL+t6cH3MbK__5XYcOkOL=Hh3-EE3SokzwQcz_XBbM2WKPZEuQ@mail.gmail.com>
To: Kris Craig <kris.craig@gmail.com>
Cc: John LeSueur <john.lesueur@gmail.com>, Arvids Godjuks <arvids.godjuks@gmail.com>, 
	internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Complete case-sensitivity in PHP
From: theanomaly.is@gmail.com (Sherif Ramadan)

> Could you elaborate? =A0Aside from making PHP forgiving of typos and over=
all
> laziness on the part of the coder, and of course BC notwithstanding, I'm =
not
> sure I understand what benefit there is to preserving this inconsistent
> behavior.
>

Kris,

Sorry, first to be clear I made a typo there, but what I'm saying is
PHP currently doesn't care if you do the following:

<?php

function Foo() { }

/* these all work the same obviously */
foo(); Foo(); FOO();

?>

However, it does care if you do the following:

<?php

$foo =3D 'bar';
$Foo =3D 'baz';
$FOO =3D 'quix';

?>

I'm not saying I'm in favor of making PHP case-insensitive. I think
it's fine that it is case-sensitive since it deals with mostly
everything on a binary level. I think the fact that it currently does
allow ASCII case-insensitivity for method/function/class/(and
partially constant) names is somewhat confusing though. It should
probably be either all case-sensitive or not. As you can argue that
there seems to be little reasoning behind wanting $foo and $FOO to be
two different things, but hey that's the arguable part.

I can't see much reason to breaking any of this now though. I don't
know about others, but I've rarely ever written or worked with PHP
code where function/method names were in anything other than ASCII and
me or anyone else cared about case-sensitivity there. I say it's fine
the way it is and I don't really see anyone presenting a valid use
case for why it should change.

Just my two cents.