Re: Unicode chars allowed in numbers?
| From: | Andrei Zmievski | Date: | Wed, 29 Nov 2006 15:44:59 +0000 |
| Subject: | Re: Unicode chars allowed in numbers? | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-26736@lists.php.net to get a copy of this message | ||
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, 9-13 [\t, \n, \v, \f, \r]) allowed? Thanks again, Matt ----- Original Message ----- From: "Andrei Zmievski" Sent: Friday, November 10, 2006--PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.phpHi 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 (and 'a'-'z' equivalents for bases > 10)?Correct.I ask because in zend_u_strtol(), HANDLE_U_NUMERIC() for array keys, etc., the u_digit() function is used, which also allows non-ASCII, higher- value digit characters, doesn't it? But then in is_numeric_unicode(), when checking for hex numbers, the ASCII values '0' and 'x' are used, which is what I'd expect after reading README.UNICODE.You're correct here again, u_digit() should not be used there. -Andrei