The only problem is that it breaks the API. What do people think?
I'm also considering removing empty_string completely but I still need to look through all of the code and try to evaluate the performance change due to it (We don't have to check each time we free a string if it's empty but on the other hand we use emalloc() to allocate empty strings).
Andi
At 10:39 PM 3/27/2003 +0200, moshe doron wrote:
shalom,
i'm writing php extension for allegro (http://www.talula.demon.co.uk/allegro/) that hopfeully 'll go somewhere soon into pecl. allegro is cross platform grafix library so in addition to the gaming capabilities, we have here chance using it as base to native php gui.
the problem i have is that both zend and allegro define empty_string. so i had to replace zend & php empty_string into ze_empty_string. the question are: 1. is used on so potential common name by zend is zend compatible naming standards (if there are)? 2. is there any chance replacing the empty_string on zend & php core with ze_empty_string or something other while defining something like:
#ifndef ALREADY_HAVE_EMPTY_STRING #define empty_string ze_empty_string #endif
for bc.
thanx moshe. ---
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
