Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:85322 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 6793 invoked from network); 20 Mar 2015 20:01:07 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 Mar 2015 20:01:07 -0000 Authentication-Results: pb1.pair.com smtp.mail=bowersbros@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=bowersbros@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.42 as permitted sender) X-PHP-List-Original-Sender: bowersbros@gmail.com X-Host-Fingerprint: 74.125.82.42 mail-wg0-f42.google.com Received: from [74.125.82.42] ([74.125.82.42:34237] helo=mail-wg0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 51/76-64120-18C7C055 for ; Fri, 20 Mar 2015 15:01:07 -0500 Received: by wggv3 with SMTP id v3so98108572wgg.1 for ; Fri, 20 Mar 2015 13:01:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Fb6LjSE20ZvshUa4Jo3dQ5tY+Mg7koGaVVgLSNxNYr8=; b=Jo/k8LT0D5QCxsHcPkGU2UOQRAb9C4Fa2oy+dsDc9I/bCJO+M/QRDVLa2K5hLR1P9X BX5jMac8CIQaaiw9JKjAId1YC7Xsv3XdsxD9TJ6BKotLfKrkhu+ts6N3yOPEr5ufS38Z OpIuE6/t+hjqRpdWrA222MW1BS5RMp/ZiJmKdX29l6ryyZs1BfSpI6D5Xz5qKheIBtXe uasZO9ZnVFXEBCaXcxNpLahzVxPD8RBoLPtdviLC1RufR/2nWnpP8lNFOvdo1ySULTKo LGjSOCkX1nGNDzGYV8qQu4XZGUfO9b8Am6HujY27cy/TkU6BRR/5xpqAK9cgmnfoIA7D rcrA== MIME-Version: 1.0 X-Received: by 10.180.211.144 with SMTP id nc16mr27870001wic.82.1426881663226; Fri, 20 Mar 2015 13:01:03 -0700 (PDT) Received: by 10.28.62.84 with HTTP; Fri, 20 Mar 2015 13:01:03 -0700 (PDT) In-Reply-To: <23A888B3-4493-4720-A275-D820F8E07F58@zort.net> References: <550B5A81.1090706@gmail.com> <550B7189.4040608@gmail.com> <7486C296-7535-4633-AFE2-02E7BBC67BC5@gmail.com> <550C1176.9050307@gmail.com> <550C1AE4.8090607@gmail.com> <550C1EC3.8000106@gmail.com> <550C317E.8020508@gmail.com> <550C6422.6080009@gmail.com> <23A888B3-4493-4720-A275-D820F8E07F58@zort.net> Date: Fri, 20 Mar 2015 20:01:03 +0000 Message-ID: To: John Bafford Cc: Rowan Collins , Leigh , PHP Internals Content-Type: multipart/alternative; boundary=001a11c26890ac5acc0511bdc6c6 Subject: Re: [PHP-DEV] RFC - Array slice syntactic sugar From: bowersbros@gmail.com (Alex Bowers) --001a11c26890ac5acc0511bdc6c6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable > > The concept itself can still work, but it=E2=80=99d need a token other th= an @. This is the symbol currently being used for examples, but thats all it is currently. Nothing is set in stone (and most likely will change), not just for this reason but for the reason that I mentioned earlier in the thread that the @ symbol has bad connotations, and avoiding these connotations would benefit the RFC. I posted four suggestions earlier, They were: @ & * ^ My favourites are the asterisk or caret. --001a11c26890ac5acc0511bdc6c6--