>
> It will be nice to have functions like this: isNumber(char),
> isAlphabetic(char), isWhitespace(char) ...
>
> It is on the plan or not?
its done already, just not committed yet...
clayton
""Ondrej Ivanic"" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Andrei Zmievski wrot
agreed, but the point was more about the implementation than how the mode is
set. a function call is good enough for me.
clayton
"Derick Rethans" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> On Sun, 14 Aug 2005 [EMAIL PROTECTED] wrote:
>
>> Andrei,
>> it was controlled by
Andrei,
it was controlled by an ini setting. there are certain APIs that take or
return offsets, so translation
was done in those instances depending on the setting. Here's an example
(it's not currently implemented
this way, though..) since my concern was only the extension, i didnt touch
the
Back in the early days of the extension, i had a request global
ICUG(codepoint_semantics) which controlled this. Setting this to false would
revert to code-unit indexing (which ICU does internally).
clayton
"Andrei Zmievski" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
>
> Then
i dont consistently agree with Zeev's opinions, but what was that for ???
l0t3k
"Jani Taskinen" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> On Sun, 14 Aug 2005, Zeev Suraski wrote:
>
>> worried about the wholesale mode that internals@ switched into, the
>> almost unanimous "YES
Wez,
UCS2 is limited to the representing characters within the BMP ( 1 code-unit
== 1 code-point)
UTF16 uses surrogates to address characters beyond the BMP (so a code-point
may be represented by 2 code-units)
clayton
"Wez Furlong" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
"Wez Furlong" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
Umm, don't we use UCS2 internally?
actually ICU is UTF16...
l0t3k
--Wez.
On 8/13/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Wez,
>
> > + case IS_UNICODE:
> > + V_VT(v) = VT_BSTR;
> > + V_BSTR(v) = SysAllocString
Wez,
> + case IS_UNICODE:
> + V_VT(v) = VT_BSTR;
> + V_BSTR(v) = SysAllocString(Z_USTRVAL_P(z));
> + break;
my understanding is that Win32 uses UCS2, so do we need to account for
surrogates ?
l0t3k
""Wez Furlong"" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> wez Sat Aug 13 15:
Wez,
zend_unicode.c may be a good bet, since the engine has to deal with
various encodings anyway (script, output, runtime)
clayton
"Wez Furlong" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
Since this cache needs to always be present (to avoid crazy
conditional compilation) w
Dmitry,
i'm glad its fixed, but i was hoping it wouldnt get fixed this way ;-)
maybe a lower impact way would have been to move the use of U_CLASS_ENTRY
into zend_parse_parameters, zend_throw_exception, instanceof_function etc ?
clayton
""Dmitry Stogov"" <[EMAIL PROTECTED]> wrote in message
Index: Zend/zend_compile.c
===
RCS file: /repository/ZendEngine2/zend_compile.c,v
retrieving revision 1.650
diff -u -r1.650 zend_compile.c
--- Zend/zend_compile.c 11 Aug 2005 23:34:55 - 1.650
+++ Zend/zend_compile.c 12 Aug 2005 04:
i would commit if i had write access...
Index: ext/standard/string.c
===
RCS file: /repository/php-src/ext/standard/string.c,v
retrieving revision 1.447
diff -u -r1.447 string.c
--- ext/standard/string.c 11 Aug 2005 23:35:59 - 1.4
val,
you dont clamp at the lower bound. suppose offset == -LONG_MAX
l0t3k
"val khokhlov" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Hello,
>
>a small patch that allows using negative value for offset in
> $string{offset}
>$string = "test";
>$string{-1} -> last 't
Jeff,
read my reply to Christian. as i mentioned, i'm working on another
project which already has infrastucture for dealing with similar issues. i
simply noticed that it could be adapted for the PAR/PHAR idea. IOW, the
extension will be written whether or not we do the implement web archives
"Christian Schneider" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> The advantage of a proven format and being able to use standard tools are
> priority #1 IMHO.
>
>> manipulate them. The advantage over other formats is that the resources
>> can be used in-place using a custom P
15 matches
Mail list logo
