What kinds of things should I avoid if I want to support PHP OpCode Caches? Are static calls evil? What about __autoload?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
What kinds of things should I avoid if I want to support PHP OpCode Caches? Are static calls evil? What about __autoload?
For every PHP-based web-application I’ve worked on for the past 3 years and a half, I’ve always used APC as an opcode cache, on all the servers I’m using…
… And I’ve never had to take of anything “special” while developping : in every case, using APC or not has been transparent, the only difference being about performances.
I’ve never had any problem with static calls, nor autoloading, for instance — nor with anything else (And I’ve worked with a couple of different Frameworks and OSS Applications)
Still, one good habit : if you plan to use APC on your production server, also use it on your development machines, just in case — but enable the
apc.statoption on those, so your life is not complicated by the opcode caching mecanism.