Re: About functions
| From: | Marcin Kurzyna | Date: | Tue, 24 Mar 2009 10:03:14 +0000 |
| Subject: | Re: About functions | ||
| References: | 1 2 | Groups: | php.pecl.dev |
| Request: | Send a blank email to pecl-dev+get-6251@lists.php.net to get a copy of this message | ||
shire pisze:
These are in CVS Head and are experimental. You'll have to look at the code comments to see what the arguments are currently: PHP_FUNCTION(apc_bin_dump); PHP_FUNCTION(apc_bin_load); PHP_FUNCTION(apc_bin_dumpfile); PHP_FUNCTION(apc_bin_loadfile);I could have (to be frank i didn't have time to look at the source yet to see whether this s applicable); any way - serialization of closures. i even had a thread about it at internals couple months ago and although i never implemented anything in the end there were two possibilities discussed: 1) APC based opcode serialization (dump(?)) 2) saving of initial fnction source (string) and recompiling it on deserialization therefore apc_bin_* sound like could be used for (1) while apc_compile_string() could be used for (2). is this a strong use case? and may be you have already thought about it? mkapc_compile_string(),There's a feature request for doing something like apc_eval already, I suppose it's something that could be added I'm just rightly nervous about eval() in general. Do you have a strong use case for this?