> > On the other hand, the latter one could be named 'RFC process', since it
> > hasn't yet been defined what the heck it is precisely...
> RFC.. Request For Comments, its as simple as that someone posts a document
> outlining what they want changed/want to do, calls it an RFC and is
> litterally making a request for comments on their idea. I think this is a
> good idea for large things but if we encourage too much we will suddenly
> flooded with RFC's all over the place then they begin to conflict.. I
> that if someone feels somthing is really important then an RFC is a good
> idea but I certainly dont want a couple a week to plough through.

That PEP's seem to work quite well, there needs to be some selection on
it... For example: several supporters before you may even start an
(official) RFC for example.

The work on Zend Engine 2 has now started, _without_ a proper definition of
it. IMHO, that's not the ideal situation, since this could lead to strange
inconsequences, because the precise behaviour is decided during
implementation. For example bug 10437, which wouldn't have existed if the
zend engine was properly defined _before_ it was implemented. But it simply
was the easiest way to implement it...

As you say, for 'light' changes, no official RFC should be created, it isn't
necessary, mainly because:
> at the moment there is no democratic process in PHP, people
> just do what they want


PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to