Re: class names with and without opcache
| From: | Greg | Date: | Thu, 19 Jun 2014 14:53:39 +0000 |
| Subject: | Re: class names with and without opcache | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-74991@lists.php.net to get a copy of this message | ||
I've uploaded some sample code. https://github.com/devosc/opcache_disabled_test
I'd appreciate it if someone could confirm whether this is a problem
because it may not be possible to use 5.5 with opcache enabled (cli
unit tests will be broken).
On Tue, Jun 17, 2014 at 10:30 PM, Greg <devosc@gmail.com> wrote:
> Hi Stas,
>
>
> Thank you, I appreciate this. I've uploaded some sample files to
> github, it uses composer as the autoloader
>
> https://github.com/devosc/opcache_disabled_test
>
> Even if I am wrong in my implementation, there should not be any
> difference/errors when opcache is disabled.
>
> I actually prefer the improvements provided by opcache since we don't
> have to come up with weird aliases like BaseConfigInterface.
>
>
> Regards,
>
>
> Greg
>
>
>
> On Tue, Jun 17, 2014 at 6:21 PM, Stas Malyshev <smalyshev@sugarcrm.com> wrote:
>> Hi!
>>
>>> Sorry to bug you, but I'd like to know if the problem I'm experiencing
>>> with opcache and 5.5 is just my end or if this is a problem for
>>> everybody. Could you let me know? Below is my original message to the
>>> mailing list.
>>
>> I didn't have time to look into it yet, but I'll try to look - most
>> likely on the weekend, if nobody beats me to it.
>> --
>> Stanislav Malyshev, Software Architect
>> SugarCRM: http://www.sugarcrm.com/
>> (408)454-6900 ext. 227
>
>
>
> --
> Greg
--
Greg