Re: Re: [ZEND-ENGINE-CVS] cvs: ZendEngine2 / zend.c
| From: | Marcus Boerger | Date: | Tue, 16 Aug 2005 20:26:21 +0000 |
| Subject: | Re: Re: [ZEND-ENGINE-CVS] cvs: ZendEngine2 / zend.c | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-18183@lists.php.net to get a copy of this message | ||
Hello Andrei,
if unicode is enabled we could handle all property/class and function
names as unicode internally and as native strings if unicode is disabled.
However that would be a slowdown, so i asked which is better, ease of coding
or speed. Anyway i'd like to have property keys always be stored in one
string represenation so when class or property name is unicode then store
the whole thing as unicode and else store it as native strings. This
involves that we store any property names as unicode if the classname is
stored as unicode. This parses better?
marcus
Tuesday, August 16, 2005, 9:31:53 PM, you wrote:
> I couldn't parse this. Could you restate your question?
> -Andrei
> On Aug 16, 2005, at 11:40 AM, Marcus Boerger wrote:
>>
>> Another thing is if we simply shouldn't treat all class/prop/fun
>> names as
>> native strings if unicode is off and as unicode strings if it is on.
>> Or do
>> you guys think that would be a too great slowdown?
>>
Best regards,
Marcus