Andi Gutmans wrote:
No, you should say that only [a-zA-Z_\x7f-\xff][a-zA-Z0-9_\x7f-\xff]*
are valid.
In addition, maybe post 5.0 we will unify global const and class const
and then it'll definitely not work with those weird names. There are
also plenty of weird things you can do with C which ar
I know. I was just giving you a +1 :)
At 07:26 PM 5/9/2004 +0200, Derick Rethans wrote:
On Sun, 9 May 2004, Andi Gutmans wrote:
> No, you should say that only [a-zA-Z_\x7f-\xff][a-zA-Z0-9_\x7f-\xff]* are
> valid.
That's what I said ;-)
Derick
--
PHP Internals - PHP Runtime Development Mailing Li
On Sun, 9 May 2004, Andi Gutmans wrote:
> No, you should say that only [a-zA-Z_\x7f-\xff][a-zA-Z0-9_\x7f-\xff]* are
> valid.
That's what I said ;-)
Derick
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
No, you should say that only [a-zA-Z_\x7f-\xff][a-zA-Z0-9_\x7f-\xff]* are
valid.
In addition, maybe post 5.0 we will unify global const and class const and
then it'll definitely not work with those weird names. There are also
plenty of weird things you can do with C which aren't defined.
Andi
Derick Rethans wrote:
On Fri, 7 May 2004, Mehdi Achour wrote:
Should I change the documentation to say that ".*" can be a constant name, but
that we recommand [a-zA-Z_\x7f-\xff][a-zA-Z0-9_\x7f-\xff]* ?
Just leave it as is.
I wanted to complete the TODO commented on languages/constants.
On Fri, 7 May 2004, Mehdi Achour wrote:
> Should I change the documentation to say that ".*" can be a constant name, but
> that we recommand [a-zA-Z_\x7f-\xff][a-zA-Z0-9_\x7f-\xff]* ?
Just leave it as is.
Derick
> Mehdi Achour wrote:
> > Hi !
> >
> > The manual reads :
> >
> > "The name of a co
Should I change the documentation to say that ".*" can be a constant name, but
that we recommand [a-zA-Z_\x7f-\xff][a-zA-Z0-9_\x7f-\xff]* ?
Mehdi Achour
Mehdi Achour wrote:
Hi !
The manual reads :
"The name of a constant follows the same rules as any label in PHP. A
valid constant name starts
