Re: RFC: PEAR Changes / Scope

On Sat, 10 Nov 2001 16:43:25 -0600, Lux wrote: >1. I propose that PEAR be split into CORE and an EXT (or CONTRIB), where >CORE is the stuff we've already got, Do you mean, that core should be both the current stuff from /php4/pear and /pear? I think, that there are already some things, that don't belong into core: DB_Pager, HTTP_Upload, MP3_Id, Net_Ping, Template_PHPLIB, XMMS, just to name a few. >and the stuff that has to go >through a rigorous approval process. Basically, Java's standard >library. +1 >EXT would be code that conforms to a certain level, but less >so than CORE. Duplication would be allowed in EXT, but we would still >be talking about classes, not apps or forums or builders. So we will not allow complete applications even in EXT? >[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. >7. 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? - Martin