Re: Making it easier to leverage APC
| From: | Rasmus Lerdorf | Date: | Sun, 03 Dec 2006 14:36:21 +0000 |
| Subject: | Re: Making it easier to leverage APC | ||
| References: | 1 2 3 | Groups: | php.pecl.dev |
| Request: | Send a blank email to pecl-dev+get-4386@lists.php.net to get a copy of this message | ||
Pierre wrote:
> By the way, the same applies to the include_once against include myth
> (which is becoming as known as condition include).
>
> But what can be done? Should "we" stop to talk about this only because
> the possible confusions? :)
People just need to learn how to profile their stuff.
By the way, there are some other interesting issues with conditional
includes if they are mixed with non-conditional ones and involve
inheritance. If a child class definition is in a top-level include but
the parent class is in a conditional include, or if you have a mixture
of conditional and top-level includes for the same set of files that
define an inheritance chain, you end up with a mixture of early and late
binding which gets really really messy. Right now APC will optionally
spew a warning message on this case and simply not cache at all when it
encounters this.
-Rasmus