Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:74666 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 21523 invoked from network); 1 Jun 2014 18:13:35 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Jun 2014 18:13:35 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 108.166.43.99 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 108.166.43.99 smtp99.ord1c.emailsrvr.com Linux 2.6 Received: from [108.166.43.99] ([108.166.43.99:37992] helo=smtp99.ord1c.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 4F/A0-15017-D4D6B835 for ; Sun, 01 Jun 2014 14:13:33 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp5.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 562151B04F3; Sun, 1 Jun 2014 14:13:30 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp5.relay.ord1c.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 0A6A71B04EC; Sun, 1 Jun 2014 14:13:29 -0400 (EDT) Message-ID: <538B6D49.3030402@sugarcrm.com> Date: Sun, 01 Jun 2014 11:13:29 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Andrea Faulds , PHP internals References: <6E3D6B3F-1BD6-42A2-B59C-12B9D6D597ED@ajf.me> In-Reply-To: <6E3D6B3F-1BD6-42A2-B59C-12B9D6D597ED@ajf.me> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] [RFC] Bare Name Array From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > That’s a whole five characters, seven including spaces, for your most > common case (identifier-like key). In JavaScript, you can avoid > quoting the key for this common case. I propose something similar for > PHP. Where the key fits the profile of IS_STRING, this RFC proposes > that you can do this instead: > > stringKey: 3, You can already do stringKey => 3 :) And saving characters is not really a big priority. Changing language syntax and making millions of people to learn new syntax just to save a couple of chars does not look like a big win to me. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227