At 01:29 PM 5/4/2001 +0300, 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
[Zeev Suraski [EMAIL PROTECTED]]
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
Let's not worry about the versions right now; I'm mostly interested in
getting feedback about the concept itself.
Zeev
At 14:30 4/5/2001, Stig Sæther Bakken wrote:
[Zeev Suraski [EMAIL PROTECTED]]
I think that there are two ways to look at the issue that John raised.
One, is a cosmetic
Let's not worry about the versions right now; I'm mostly interested in
getting feedback about the concept itself.
Making PHP case sensitive seems like a good idea. (I've always wondered
why
bits of it were and bits weren't, to be honest.)
I agree on this one too. What about writing a
At 15:34 4/5/2001, Edin Kadribasic wrote:
I agree on this one too. What about writing a migration tool that can fix
the existing code automagically?
It'll be possible. Let's take it one step at a time though...
Zeev
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail:
At 15:32 4/5/2001, John Parker wrote:
Hmm... hope Sterling's work on ADT (sweet, sweet ADT, drool, etc.) isn't
delayed due to this. (Doubt it would be, but you never know.)
ADT? (I know what it means, but not in the context of PHP)
Zeev
--
PHP Development Mailing List http://www.php.net/
To
Hmm... hope Sterling's work on ADT (sweet, sweet ADT, drool, etc.) isn't
delayed due to this. (Doubt it would be, but you never know.)
ADT? (I know what it means, but not in the context of PHP)
It was briefly mentioned on the Weekly Summary for 23/03/01 on the Zend web
site.
Ah; I'd imagine it'll be implemented as an extension module and not on the
language level, so it shouldn't be related in any way.
Zeev
At 15:56 4/5/2001, John Parker wrote:
Hmm... hope Sterling's work on ADT (sweet, sweet ADT, drool, etc.) isn't
delayed due to this. (Doubt it would be,
Zeev Suraski wrote:
ADT? (I know what it means, but not in the context of PHP)
Sterling is working for some time now on a ADT extension for PHP, that
offers native PHP data-types for Lists, Trees, ...
--
sebastian bergmann[EMAIL PROTECTED]
Zeev Suraski wrote:
It would also improve performance fairly significantly.
Just curious, since I don't know the 'inner magic' of the ZendEngine:
Why do you expect a performance improvement by introducing case
sensitivity for class/function names?
--
sebastian bergmann
On Fri, 4 May 2001, Sebastian Bergmann wrote:
Zeev Suraski wrote:
It would also improve performance fairly significantly.
Just curious, since I don't know the 'inner magic' of the ZendEngine:
Why do you expect a performance improvement by introducing case
sensitivity for class/function
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
From zend_execute.c:
tmp = *function_name;
zval_copy_ctor(tmp);
convert_to_string(tmp);
function_name = tmp;
zend_str_tolower(tmp.value.str.val, tmp.value.str.len);
That can be avoided
Quoting Zeev Suraski [EMAIL PROTECTED]:
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,
Zeev Suraski schrieb:
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
At 16:45 4/5/2001, Wez Furlong wrote:
Stig suggested making it case-insensitive by default until 4.2; I think
that has a higher WTF factor than making it case sensitive in 4.1
I truly suggest to keep the version number issue to some other time...
Zeev
--
PHP Development Mailing List
On 2001-05-04 14:45:48, Wez Furlong [EMAIL PROTECTED] wrote:
that has a higher WTF factor than making it case sensitive in 4.1
4.0 I mean.
--Wez.
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On Fri, 4 May 2001, Zeev Suraski wrote:
IMHO, in a compatibility breaking upgrade, we should look into defaulting
to case sensitivity, while allowing case insensitivity as a non-default option.
+1
--Jani
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL
On Fri, 4 May 2001, Zeev Suraski wrote:
IMHO, in a compatibility breaking upgrade, we should look into defaulting
to case sensitivity, while allowing case insensitivity as a non-default
option.
+1 from me too.
-Chris
--
PHP Development Mailing List http://www.php.net/
To unsubscribe,
IMHO, in a compatibility breaking upgrade, we should look into defaulting
to case sensitivity, while allowing case insensitivity as a
non-default option.
+1
+1
=)
Peter [DiSAStA] Petermann
On Fri, 4 May 2001, Zeev Suraski wrote:
IMHO, in a compatibility breaking upgrade, we should look into defaulting
to case sensitivity, while allowing case insensitivity as a non-default option.
Zeev
That solves my problem and makes me happy.
+1
--
John Donagher
Application Engineer
21 matches
Mail list logo
