Re: opcache_compile_file() declares top-level functions

>> On 21 November 2024 10:48:46 GMT, Daniil Gentili <daniil.gentili@gmail.com >> <mailto:daniil.gentili@gmail.com>> wrote: >> >I speak for myself (and some others, as can be seen by pull requests on some FOSS >> >projects, which made pull requests to account for this behaviour), as a user of preloading who has >> >encountered this behaviour, understood the reason for it and made the required changes to keep using >> >it. >> >> This is still painfully vague. What projects? What "reason for it" did you >> understand? When you say projects accounted for it, do you mean they got some benefit from it, or >> that they worked around the problems it caused them? I confused the linked issue with another issue related to preloading that I encountered and worked around with include guards (https://github.com/amphp/amp/issues/321). >> Note that we are not talking about preloading, as a general concept; we are talking about >> the specific function opcache_compile_file. That function's explicit purpose is to prime the >> opcache *without* behaving the same way as including the file. Yep, this makes sense, completely missed that when reading the initial issue :) > > Seems like function autoloading would alleviate this use case and make this behavior easier to > deprecate. > +++