Hi Pierre,
:-O I was just going to give you an example from zend_operators.h,
is_numeric_string() and guess what? It's the "correct" way that I thought
it should be! I thought PHP 6 changed something, to where
/* handle hex numbers */
if (length>=2 && str[0]=='0' && (str[1]=='x' || str[1]=='X')) {
conv_base=16;
}
which is easy to understand :-) became
if (length>=2 && str[0]=='' && (str[1]=='x' || str[1]=='X')) {
conv_base=16;
}
BUT, I recently started looking at http://lxr.php.net so I could
cross-reference, etc., instead of searching my local sources, and that's
where I first saw this "change." It took you asking for an example for me
to realize that LXR is the problem, screwing up the display of '0' !
(Though I *think* I saw it correctly in some places?) LOL, I can't believe
it. I kinda thought, "Oh well, I just don't get it," but I'm glad I
e-mailed before spending more time than I have trying to figure out what the
empty char constant does!
http://lxr.php.net/ident?i=is_numeric_string -- check out 12 lines into the
function definition. :-/
Well, thanks for helping me get on the right track to "solving" this. The
LXR thing needs fixing I guess.
Matt
----- Original Message -----
From: "Pierre"
Subject: Re: [PHP-DEV] Use of "empty character constant?"
> On 7/8/06, Matt W wrote:
> > Hi Pierre,
> >
> > Thanks for the reply, but where does that page talk about an EMPTY
character
> > constant? I pretty much understand character handling otherwise. :-)
>
> Then I do not understand your question. Do you have the exact
> error/warning/notice? And some example code?
>
> --Pierre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
