On Tue, 14 Aug 2001, John Donagher wrote the following to [EMAIL PROTECTED]:
> With what end in mind is an RFC to be created for? In the IETF, RFC's are
> typically long, complex, and authoritative. They are often referenced for years
> after their inception. Do you honestly think we could (or want to) achieve this
> with PHP feature RFC's? Or will they be used only before initial feature
> implementation, then quickly outdated and discarded? That is my biggest problem
> with documents: they take a lot of effort to create, are often difficult to
> grok, and _almost always_ have a very short lifecycle.
PHP feature RFC != IETF RFC's.
Go back and read my original proposal on the issue. What I had in mind
was something more like what Perl has done with the Perl 6 RFC's, or
(perhaps) the PEP's of Python...
The point being that there is a LOT of discussion on certain topics, and
people often change sides on an issue over the life of the discussion. I
was simply trying to say "Let's make this a *bit* more orderly.", mainly
becuase I had already lost track of several of the then-current threads
on the zend-engine list.
--
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]
