Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:60020 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 58754 invoked from network); 16 Apr 2012 21:30:48 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Apr 2012 21:30:48 -0000 Authentication-Results: pb1.pair.com header.from=tom@punkave.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=tom@punkave.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain punkave.com designates 209.85.161.170 as permitted sender) X-PHP-List-Original-Sender: tom@punkave.com X-Host-Fingerprint: 209.85.161.170 mail-gx0-f170.google.com Received: from [209.85.161.170] ([209.85.161.170:57525] helo=mail-gx0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E0/DF-05733-68F8C8F4 for ; Mon, 16 Apr 2012 17:30:47 -0400 Received: by ggmb2 with SMTP id b2so3132695ggm.29 for ; Mon, 16 Apr 2012 14:30:44 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding:x-gm-message-state; bh=ZMvBAA5vKp6rdo/t/WpTNg844uQ9btu6NrS7RvTp6O0=; b=E1M5J4UKnVC5S6M2nUTZoKspnZZEm23C7L5g9A6phlannJTkNzLe2rtjQPryvHIsSg +pya+Y8RqPkaMVHSLgYit56Op3Modk6ridauDGUvkKpxsimExJ5oGMlK8MCUsDrgkXPG EikQh7TLQHJjv5hd51o+70kvQQ67Mcdd0eUDJmbc8QxRVZRcKuSOvyqbGJUOIrh5fvX8 xm3vRwM9uwTsKvqzGdly0YNhR0xEg6ZE1r/FI7FRDHaGkwxxiyf7s7AkFcLgRrJaSiey gCURIetFfjGTGtm5mHpbxpuQud/ngEogwePfvuQLj7XK7NefWgAos9nwJ7n80Eu7ACvt /6sg== MIME-Version: 1.0 Received: by 10.101.129.3 with SMTP id g3mr3773830ann.9.1334611844084; Mon, 16 Apr 2012 14:30:44 -0700 (PDT) Received: by 10.101.57.14 with HTTP; Mon, 16 Apr 2012 14:30:43 -0700 (PDT) In-Reply-To: References: <4F8C577D.4010303@developersdesk.com> <4F8C757C.1020400@developersdesk.com> Date: Mon, 16 Apr 2012 17:30:43 -0400 Message-ID: To: PHP Internals Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQm4XUcj8xWMq/3J8l/c89XTk/P/abVdijqVyhFpCHOFl2rPGkKo/rrocqSblJBEnWffy5e8 Subject: Re: [PHP-DEV] Re: Go for votes for the open tag-less PHP files From: tom@punkave.com (Tom Boutell) This has been added in version 1.1.1 of the source_files_without_opening_tag RFC: https://wiki.php.net/rfc/source_files_without_opening_tag On Mon, Apr 16, 2012 at 5:25 PM, Tom Boutell wrote: > I think the 'as' solution is smart. > > On Mon, Apr 16, 2012 at 3:54 PM, Kris Craig wrote: >> On Mon, Apr 16, 2012 at 12:51 PM, Nikita Popov wrote: >> >>> On Mon, Apr 16, 2012 at 9:39 PM, Rick WIdmer >>> wrote: >>> > On 4/16/2012 1:02 PM, Kris Craig wrote: >>> >> >>> >> On Mon, Apr 16, 2012 at 10:31 AM, Rick >>> >> WIdmerwrote: >>> >>> >>> >>> >>> >>> More important include doesn't currently allow multiple parms: >>> >>> >>> >>> =A0 include "foo.bar", 'baz'; >>> >>> >>> >>> Parse error: syntax error, unexpected ',' in bla.php on line xx >>> >> Regarding include/require, I agree that any BC break would be extrem= ely >>> >> minimal. =A0In the 10+ years I've been developing PHP, I don't think= I've >>> >> ever once seen somebody include multiple scripts on a single line (I >>> >> wasn't even aware that such a thing was allowed). >>> > See above. =A0It is not allowed now. >>> >>> I think there is a misunderstanding here. Inclusions with two >>> arguments are currently not allowed, yes. The point is that adding >>> such a second argument would make the grammar ambiguous. >>> >>> E.g, consider this: >>> >>> func(include 'foo', $someThing); >>> >>> Currently this is interpreted as the return value of 'foo' and the >>> variable $someThing being passed to func. >>> >>> If you add a second argument it's unclear what this does. Is this a >>> two-argument include? I.e. should it be interpreted as >>> >>> func((include 'foo', $someThing)); >>> >>> Or is this a one-argument include and should be interpreted as >>> >>> func((include 'foo'), $someThing); >>> >>> In my eyes such an ambiguity renders any proposal to add another >>> argument to include completely unacceptable. >>> >>> The only option is to add a dedicated syntax for it like >>> >>> include 'foo' as $flags; >>> >>> Nikita >>> >>> -- >>> PHP Internals - PHP Runtime Development Mailing List >>> To unsubscribe, visit: http://www.php.net/unsub.php >>> >>> >> Hmm I like that idea. =A0Anyone see any downsides to using "as" instead = of >> comma delination? >> >> --Kris > > > > -- > Tom Boutell > P'unk Avenue > 215 755 1330 > punkave.com > window.punkave.com --=20 Tom Boutell P'unk Avenue 215 755 1330 punkave.com window.punkave.com