On Fri, 04 May 2001, Zeev Suraski wrote:
> I think that there are two ways to look at the issue that John raised.
>
> One, is a cosmetic change, that would add a bit of bloat to classes, and
> retain another name in them. Allowing access to it using some specialized
> function (get_beautiful_class_name() or something like that).
>
> The other, is a more fundamental change, and it is to change PHP to be case
> dependant. PHP 4.0 follows the standard set by PHP/FI 2.0 (or earlier),
> and maintains case sensitivity for variable names, but not function names
> or class names. IMHO, there's very little reason for this inconsistency,
> and PHP would have been better off with full case sensitivity across class
> names, function names and variable names. It would also improve
> performance fairly significantly.
>
> IMHO, in a compatibility breaking upgrade, we should look into defaulting
> to case sensitivity, while allowing case insensitivity as a non-default option.
+1.
-Andrei
It is commonly the case with technologies that you can get
the best insight about how they work by watching them fail.
-- Neal Stephenson
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
