Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:103503
MIME-Version: 1.0
References: <BY1PR02MB12606B0B2C6878B6F73D151BBFD40@BY1PR02MB1260.namprd02.prod.outlook.com>
 <CAF+90c_6Vwz+GguSfCGQw5ncmcSBGXnXP4yo1KymLDMEaL19Hw@mail.gmail.com>
 <BY1PR02MB1260D6A74881B45987CC462EBFD40@BY1PR02MB1260.namprd02.prod.outlook.com>
 <F1BA9936-6BCD-47C8-90B8-B011B472A610@gmail.com> <CAJHtznxOm=YR8FcUDx_M-Fv9WgP-PtT+vg4G5_sMom2EJK5iEA@mail.gmail.com>
 <1cb7fecd-22ba-0ded-5bd6-e70208053012@gmail.com> <7f65012b-e26a-fb58-718b-b35569e53d03@gmail.com>
 <CADyq6sLWz3rZaPCu-AZtCoKCQGC4SiJra66w+6cdeFvk58FJ_A@mail.gmail.com>
 <CAJHtznxQOnZZEhnXP-KY+iMSQ-0BBwWFhHaofU2+R+=ZxXx0VQ@mail.gmail.com>
 <CADyq6sKGg6vnzqTsBprz8NuuPjnw_fZuC-it=K_ExoBnoXRcbw@mail.gmail.com> <CAJHtzny=RWQ=rNFAftwfyHjgVwX4GFVn2ZFTQ3YWd_dBLGhr_Q@mail.gmail.com>
In-Reply-To: <CAJHtzny=RWQ=rNFAftwfyHjgVwX4GFVn2ZFTQ3YWd_dBLGhr_Q@mail.gmail.com>
Date: Mon, 26 Nov 2018 10:46:59 +0000
Message-ID: <CALKiJKrB8QpgwTMesd+Cz+DHxrxtd8s9kvjRs7xg-Z5PFugc=A@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000001f672d057b8f0e9d"
Subject: Re: [PHP-DEV] declare(cache=0) - explanation (was: Re: [PHP-DEV]
 [mini-RFC] Disable opcache per script using "declare(cache=0)")
From: rowan.collins@gmail.com (Rowan Collins)

--0000000000001f672d057b8f0e9d
Content-Type: text/plain; charset="UTF-8"

On Mon, 26 Nov 2018 at 09:15, Zeev Suraski <vsuraski@gmail.com> wrote:

> The goal of declare(cache=0) would be to avoid persisting utility
> functions/classes that have to do with a particular preload.php
> implementation - so that they don't become a part of the app's memory
> context and 'pollute' its scope.
>


Thanks for the clarification, that makes a lot more sense than the
performance impact.

As I mentioned before, though, the behaviour of the following case is not
obvious to me:

# preload.php
require 'foo.php';
require 'bar.php';

# foo.php
declare(cache=0);
class Foo {}

# bar.php
class Bar extends Foo {}

At the time it is first parsed, Bar is a complete class, and is being
defined during preload, so ought to be defined permanently; but it depends
on Foo, which will not be cached. Will this be an error, or will class Bar
simply not be defined on future requests?

Regards,
-- 
Rowan Collins
[IMSoP]

--0000000000001f672d057b8f0e9d--