Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:60299 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 77613 invoked from network); 24 Apr 2012 23:00:30 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Apr 2012 23:00:30 -0000 Authentication-Results: pb1.pair.com smtp.mail=tjerk.meesters@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=tjerk.meesters@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.210.45 as permitted sender) X-PHP-List-Original-Sender: tjerk.meesters@gmail.com X-Host-Fingerprint: 209.85.210.45 mail-pz0-f45.google.com Received: from [209.85.210.45] ([209.85.210.45:38815] helo=mail-pz0-f45.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C5/D3-54790-D80379F4 for ; Tue, 24 Apr 2012 19:00:29 -0400 Received: by dacx6 with SMTP id x6so1649416dac.18 for ; Tue, 24 Apr 2012 16:00:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:in-reply-to:mime-version:content-transfer-encoding :content-type:message-id:cc:x-mailer:from:subject:date:to; bh=GND1bx0SoysesqgVIYCgHAohs/6CuFCJf/i8P6g3S2U=; b=t9rfOljeYg+7InpX7rndhOsjes50vby0YycHsJFBx30vHxO0JtZJouG6RS+X9VXdVG 8nYQeQ4CGGp6x7vz/a2EWvDxLrzXa+ZyuLpGxz1Wji/UGZs3JPNxHHnwr9GoCvyMqHXU w+H4s6CtG5LWLh5jt7DBzrhFY6HNINXT/xYWJ19d0KXfQNhRmLwYVEmIIR22/xanH+mc 2L/UG57YxDBxbqH5tZPlZ06f2pVo2OXvZ9/RaYkXbMpESOXYqLlGWGLrL9uoFayVFg3V E6r9HCBQ2hxkbZO35/BSnEfgeBZimRpwecrZK63Ck6zvzt8Ze8LU4XSTyVBBL6XojctS SYIQ== Received: by 10.68.224.39 with SMTP id qz7mr1900570pbc.68.1335308426536; Tue, 24 Apr 2012 16:00:26 -0700 (PDT) Received: from [192.168.1.104] (bb115-66-192-159.singnet.com.sg. [115.66.192.159]) by mx.google.com with ESMTPS id d4sm18631178pbe.36.2012.04.24.16.00.23 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 24 Apr 2012 16:00:25 -0700 (PDT) References: In-Reply-To: Mime-Version: 1.0 (1.0) Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Message-ID: <9D120847-C2AB-47C4-BCE4-6F68F3C6FE06@gmail.com> Cc: Tom Boutell , PHP internals list X-Mailer: iPhone Mail (9B179) Date: Wed, 25 Apr 2012 07:00:20 +0800 To: Kris Craig Subject: Re: [PHP-DEV] [RFC] Pure PHP Scripts (Updated) From: tjerk.meesters@gmail.com (Tjerk Meesters) On 25 Apr, 2012, at 5:42 AM, Kris Craig wrote: > On Tue, Apr 24, 2012 at 1:10 PM, Tom Boutell wrote: >=20 >> * The RFC starts off immediately talking about file extensions, but >> the actual implementation proposed doesn't rely on file extensions or >> suggest any enforcement of them. That disparity should be addressed >> for clarity. >>=20 >=20 > Did you read the whole RFC? Please refer to the "Naming Conventions" > section. It addresses this explicitly. >=20 > Are you saying that section wasn't sufficiently clear or did you just miss= > it? >=20 I think what he means is that the abstract section should be, well, abstract= . Currently it appears more detailed than it should be by referring to file e= xtensions on the let go. I would phrase that section in a way that doesn't r= ely on another section to explain the used terminology.=20 Also, references such as .phpp are used throughout the document to indicate a= particular type of source file rather than an actual file extension. As suc= h I would recommend moving your terminology section to right underneath abst= ract. This would improve the readability.=20