Re: Internals read-only

Why not just letting people with @php.net accounts post to the list as well as people having the Zend Certification. That would push the certification incentives to a new high. So you either contribute or pay to write emails here :) Olivier btw: I'm joking, but yes, Jani is right on the SNR. Just don't know the right way to fix this. On Dec 13, 2007 10:50 AM, Richard Quadling <rquadling@googlemail.com> wrote: > On 13/12/2007, Jochem Maas <jochem@iamjochem.com> wrote: > > 1. most people reading the internals list already subscribed to general > > 2. general is in no way suitable for the kind of discussion currently > > occuring on internals - the difference between internals and general is akin > > to the difference between fine art and drawing with crayons. > > I'm SURE you are not implying that those that use the PHP language > (rather than the developers of the PHP language) are some how more > infantile and can only use crayons rather than wielding the fine > brushes that create the art of the language itself? > > I would say that we (those that write PHP code) are your clients and > as the client is __ALWAYS__ right, you should drop namespaces, add > discrete setters and getters to provide accessibility to class > properties and add 2 "" to the CreateProcess calls in the core to fix > to an old issue with the windows command line intepreter. > > Then, we would have some progress. > > ;-{}}} > > > >