Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:61802 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 6573 invoked from network); 26 Jul 2012 01:28:06 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 26 Jul 2012 01:28:06 -0000 Authentication-Results: pb1.pair.com header.from=lists@rotorised.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=lists@rotorised.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain rotorised.com from 117.55.227.24 cause and error) X-PHP-List-Original-Sender: lists@rotorised.com X-Host-Fingerprint: 117.55.227.24 mta24-data1.ironport2.cbr1.mail-filtering.com.au Received: from [117.55.227.24] ([117.55.227.24:15425] helo=mta24-data1.ironport2.cbr1.mail-filtering.com.au) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 40/06-08189-22D90105 for ; Wed, 25 Jul 2012 21:28:05 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AtsOAOabEFCva78L/2dsb2JhbABFukoEAwGCGAEBBThAEQsYCRYPCQMCAQIBRRMIAQGICAG8XY8lgxwDll2ENBOKMoJx X-IronPort-AV: E=Sophos;i="4.77,656,1336312800"; d="scan'208";a="45731601" Received: from ju001lcs02.dfw.the-server.net.au (HELO ju001lcs02.dfw.the-server.com.au) ([175.107.191.11]) by smtp-data2.ironport2.cbr1.mail-filtering.com.au with ESMTP; 26 Jul 2012 11:27:58 +1000 Received: from [130.102.82.223] (port=39094 helo=a82-223.nat.uq.edu.au) by ju001lcs02.dfw.the-server.com.au with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from ) id 1SuCrs-0028Km-Rw for internals@lists.php.net; Thu, 26 Jul 2012 11:27:57 +1000 Message-ID: <50109D18.3000305@rotorised.com> Date: Thu, 26 Jul 2012 11:27:52 +1000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: internals@lists.php.net References: <50105BFC.80900@ajf.me> In-Reply-To: <50105BFC.80900@ajf.me> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] RFCs and organisation From: lists@rotorised.com (Ryan McCue) Andrew Faulds wrote: > Secondly, I noticed that Python's PEPs are numbered, unlike PHP's > RFCs. Whilst they aren't quite the same thing, I wonder if this would > be useful, particularly since it provides a simple and unambiguous way > to refer to one, e.g. RFC 123 instead of "RFC on how to write an RFC". If we do that, we should call them PHP RFCs (PRFCs?) instead, to avoid confusion with IETF RFCs, otherwise it may get confusing. -- Ryan McCue