Hello,
On 11/29/06, Andrei Zmievski <[EMAIL PROTECTED]> wrote:
We should use whatever trim() uses, I think.
I think so too (more consistent).
--Pierre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
We should use whatever trim() uses, I think.
-Andrei
On Nov 29, 2006, at 5:58 AM, Matt Wilmas wrote:
Hi Andrei,
One more related question: What about for any leading whitespace with
numeric strings, like in zend_u_strtol()? Is u_isspace() needed,
or are
only the ASCII-equivalents (0x20,
Hi Andrei,
One more related question: What about for any leading whitespace with
numeric strings, like in zend_u_strtol()? Is u_isspace() needed, or are
only the ASCII-equivalents (0x20, 9-13 [\t, \n, \v, \f, \r]) allowed?
Thanks again,
Matt
- Original Message -
From: "Andrei Zmievski
Hi Andrei,
All right, glad I checked. I had a few things in mind to optimize
is_numeric_string/unicode, and it's fairly straightforward in _string, but
would just make things slower if u_* functions were needed to do the same in
_unicode, so I was going to rethink it. Now whatever I come up with
Hi Andrei, et al.,
I was just looking at README.UNICODE, regarding interpretation of
numbers:
"we restrict numbers to consist only of ASCII digits," and "Numeric
strings
are supposed to adhere to the same rules." Is it correct to take
that to
mean only UChar's with values from '0'-'9'/0x3
Hi Andrei, et al.,
I was just looking at README.UNICODE, regarding interpretation of numbers:
"we restrict numbers to consist only of ASCII digits," and "Numeric strings
are supposed to adhere to the same rules." Is it correct to take that to
mean only UChar's with values from '0'-'9'/0x30-0x39 (
