Re: on the coding standards - Re: [PEAR-DEV] PEAR Group June 24 2007 Meeting Minutes
| From: | Alexey Borzov | Date: | Mon, 09 Jul 2007 18:11:50 +0000 |
| Subject: | Re: on the coding standards - Re: [PEAR-DEV] PEAR Group June 24 2007 Meeting Minutes | ||
| References: | 1 2 3 4 5 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-47296@lists.php.net to get a copy of this message | ||
Hi,
Joshua Eichorn wrote:
Alexey Borzov wrote:Deeper in this thread Rasmus writes:Arnaud Limbourg wrote:There is a thread from oct 2006 where we got feedback from Ramsus, http://thread.gmane.org/gmane.comp.php.pear.core/4803The issue trying to be solved here is to be opcoce cache friendly.I'd really like to see something like "developer X, who maintains opcode cache Y, suggests this approach in his (tutorial|presentation|article) which can be read at [Z]." here, not just vigorous handwaving.
I personally prefer completely clean libraries that don't do any runtime checks at all. Any tricks you add will cause nasty performance penalties. autoload is especially nasty because you are forcing things out of the compiler down into the executor which again kills performance under an opcode cache.Doesn't look like an encouragement to use __autoload() to me...