most of the functions converted to FAST_ZPP were collected by profiling or real life apps. These functions spent significant part of the time in zend_parse_parameters() because they are short themselves or because they are called very often.
few functions were added to test some "exotic" type specifiers (like "C" or "L"). Thanks. Dmitry. On Fri, Sep 5, 2014 at 11:20 AM, Pierre Joye <pierre....@gmail.com> wrote: > On Fri, Sep 5, 2014 at 8:45 AM, Dmitry Stogov <dmi...@zend.com> wrote: > > It's already done for strlen() - ZEND_STRLEN opcode (and few other > > functions). > > But it make no sense to convert all useful functions into opcodes. > > We need an ability of fast parameter parsing anyway. > > Got that, but hard to say for which functions. Right now it is used > for almost everything, reflection, pcre, etc. I can hardly think about > why a faster zpp may impact these functions. Do you have an exhaustive > list? > > I am not saying it is not good to rethink zpp but if we do then the > gain from a usability point of view must be much better. I do not see > that now (yes, subjective but...). > > Cheers, > -- > Pierre > > @pierrejoye | http://www.libgd.org >
