On Wed, 7 Jan 2015, Pierre Joye wrote: > On Wed, Jan 7, 2015 at 2:14 PM, François Laupretre <franc...@tekwire.net> > wrote: > >> De : Pierre Joye [mailto:pierre....@gmail.com] > >> > >> ... here, it is proposed to bundle scripts that will be executed at > >> runtime like any other script, except that nothing can be done with > >> them, not even disable them if not required (like using its own > >> glue codes). > > > > I agree. Bundling scripts in extensions to execute them at each > > RINIT is, IMO, not a good idea (mostly for performance reasons and > > lack of control, as you note), but I keep thinking that a mechanism > > to embed PHP scripts in extensions and make them available via a > > common stream wrapper can be useful. What I don't like is the fact > > to execute them automatically at every RINIT. I prefer to let the > > extension free to load its PHP code when its logic decides it is > > needed. > > Or let the extension defines a script to prepend, preload, whatever we > end to do. > > It is however important, as you mentioned, to leave the engine and the > user the ability not to load it, at all.
No no, *not* loading the code is exactly what I want to prevent people from doing! The PHP library code is an *integral* part of the extension. Without it, its APIs and functionality would be useless. pickle, two packages, or any of that other mallargy are not going to fix this. It needs to be one package for this to work well, *without* the possibility of users messing things up. Derick
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
