On Thu, Oct 1, 2020 at 9:14 AM Dik Takken <dik.tak...@gmail.com> wrote: > > On 01-10-2020 14:30, Nikita Popov wrote: > > It would be good to know what the actual use-case for this is. If the goal > > here is to distribute pre-compiled PHP code without the source code, then > > this is not going to work without making the opcode format stable (which, I > > think, is pretty unlikely.) If the goal is improving cold startup > > performance, then I wonder what the benefit over the existing file cache is. > > The only use case I see is to package commercial closed source > applications as Docker containers. That allows the packager to ship the > compiled code along with the exact PHP version and configuration that > can run it reliably. > > Regards, > Dik Takken
Note that for PHP 8.0 we made the system ID change even more than it used to because doing so fixes sigsegvs when switching what extensions are loaded (common when trialing an APM product, or loading and unloading xdebug) when file cache is used. This means that it is even more important to have sources than in the past, and necessarily so because of real segmentation faults. So I second Nikita's opinion: this is not going to work well without stabilizing the opcode format. This may be possible, but it would be a lot of work; it's not happening soon. If you do it anyway be prepared for plenty of crash complaints. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: https://www.php.net/unsub.php
