Hi! > 1) Create the notion of "Persistent User > Functions/Classes/Constants/etc...". This is an important perf item > as reloading a prepend file on EVERY request is costly. Less costly > with an opcache, sure, but still costly. Making the entries > persistent lets us deal with this once in the process lifetime and > keep the data around.
That looks like much bigger can of worms. I.e. would these classes be immutable? Would we ban functions/methods from having static vars? How would we achieve that? etc. etc. > 2) Embedded text sections. It's possible to place the raw PHP code > into the compiled .so/.dylib/.dll file and fetch it out for > compilation at runtime. This enables easy bundling of the loaded I guess it is possible, but why - what's wrong with plain old files and phars? > scripts, obviates the need to track what directory the files are in, You still need to address the files somehow if you plan to have more than one, which would eventually lead you to the need to namespace it since people tend to name their files "utils.php". Which would be essentially the same as directories. So I'm not sure I understand the win here. -- Stas Malyshev smalys...@gmail.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
