On Sat, Nov 24, 2018 at 11:03 PM Marco Pivetta wrote:
> Adding to the pile of "it's an edge case", since the preload scripts will
> be procedural, wouldn't it be sufficient to call
> `opcache_invalidate(__FILE__)` at the end of them?
>
I suppose the only negative there would be some very minor
On Saturday, November 24, 2018 11:03:01 PM CST Marco Pivetta wrote:
> Adding to the pile of "it's an edge case", since the preload scripts will
> be procedural, wouldn't it be sufficient to call
> `opcache_invalidate(__FILE__)` at the end of them?
Are we certain that it will always be procedural?
Even if there were definitions in said script, the same issue would arise
with a directive.
On Sun, 25 Nov 2018, 18:35 Larry Garfield On Saturday, November 24, 2018 11:03:01 PM CST Marco Pivetta wrote:
> > Adding to the pile of "it's an edge case", since the preload scripts will
> > be procedural
On Sun, Nov 25, 2018 at 7:03 AM Marco Pivetta wrote:
> Adding to the pile of "it's an edge case", since the preload scripts will
> be procedural, wouldn't it be sufficient to call
> `opcache_invalidate(__FILE__)` at the end of them?
>
> That would actually not do anything useful - as the file wil
Is that space rrreally a problem?
Take the example ZF loader from the RFC: that barely makes any difference
at all.
A stronger reasoning for another language construct (that changes engine
behaviour) is kinfa required.
On 25 Nov 2018 22:34, "Zeev Suraski" wrote:
On Sun, Nov 25, 2018
OK. I didn't think, this feature required explanation. I saw this like a simple
way to separate "data" and "code".
Anyway, now I see, this can't be accepted without RFC etc
Thanks. Dmitry.
From: Marco Pivetta
Sent: Monday, November 26, 2018 12:43:15 AM
To: Zee
