Re: [ZEND-ENGINE-CVS] cvs: ZendEngine2(PHP_5_2) / zend.h zend_API.c zend_builtin_functions.c zend_compile.c zend_execute_API.c zend_object_handlers.c /tests bug43128.phpt php-src NEWS
[email protected] (Marcus Boerger)
| Newsgroups | php.zend-engine.cvs |
|---|---|
| Message-ID | <[email protected]> |
Hello Stanislav, to me the questions are more like: a) Do we really need unlimited function/method/const/variable names? b) Would it not be much better to limit those and get rid of the additional overhead c) Is it safe to use something that is marked as dangerous? marcus In case my opinion is not clear. My take is that we limit the length and go with alloca and drop the overhead. Saturday, February 16, 2008, 1:27:36 AM, you wrote: > Hi! >> well in this case as well as in most other cases we deal with unrestricted >> lengths. So adding an additional complexity does not seem very good imo. > It is important to understand the difference between potentially > unlimited length - which can come from malicious or very rare > exceptional input - and 99.9% of regular cases where the input is very > short. The improvement we get on those frequent cases covers for extra > check to accomodate the very infrequent case of the long string. > -- > Stanislav Malyshev, Zend Software Architect > [email protected] http://www.zend.com/ > (408)253-8829 MSN: [email protected] Best regards, Marcus