Re: RFC: PEAR Changes / Scope
| From: | Lux | Date: | Sun, 11 Nov 2001 09:13:43 +0000 |
| Subject: | Re: RFC: PEAR Changes / Scope | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-2799@lists.php.net to get a copy of this message | ||
Martin Jansen wrote:
So we will not allow complete applications even in EXT?There's already freshmeat, hotscripts, and the like for that. Extending PEAR into that arena as well would probably be too far from the original focus, I would say.
Sounds fair to me.[Coding Standards]A suggestion: I think the core classes should have a _totally_ unique coding standard. For ext, we can have more 'flexible' standards like the ones you suggested.
I just tried running a quick test, and they are coming up identical now. Strange. Of course, my tests from before were on a previous version of PHP so that probably explains it. I guess scratch #7, although I'm not sure my quick microtime + for loop test could be deemed conclusive. I still perfer single-quotes, less shift-key work. :) Lux7. Let's try to use single-quotes whenever possible. I tested a script I wrote that had tons of quotes in it both ways, and it made a noticeable difference. We have to stay the fastest bad-asses on the web dev scene, after all. ;)Yeah :-). Can you provide some results of your tests? IIRC someone said some time ago, that $foo,$bar is even faster than $foo.$bar. Is that right?