Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:52815 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 32543 invoked from network); 2 Jun 2011 21:22:37 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 2 Jun 2011 21:22:37 -0000 Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass; domainkeys=bad Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.42 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.215.42 mail-ew0-f42.google.com Received: from [209.85.215.42] ([209.85.215.42:51530] helo=mail-ew0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id FC/52-18291-C1FF7ED4 for ; Thu, 02 Jun 2011 17:22:37 -0400 Received: by ewy2 with SMTP id 2so500528ewy.29 for ; Thu, 02 Jun 2011 14:22:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=C7HZTxQ/auYzf4RA+ghh435joyE+iJGUQogDLLO2d9M=; b=UlUpAtGSemgu17rdbCD75Xl+vveTmZNuHFIuJTs1RdliCKVBrM+mUYOgCg5p79T+Qs UFlUpYL5m3OiqeJs9NguoVRGUF5vyUJnQCmoiL9dpYNWEMPA71lYq7jwUWf8b85bJFpU H28nfrrSNVg0dQWYaHxLw2/CDUznbouoJH/bw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=c/dbu8NdXSmajZidtQPMvnW0dtCtFy3pj+smRkSUwb3Fa15HlM+4O8fcUP7YFw2aRC OThiTKvLyuvy7g9fhkSa0MS2IgaOI1Zhn2BSnPE/hJ8uOEr99/4i/HSS4vF2oelClzdo uktRPoYe4izg+GEIouk6HD3W+6FfRolqW3eLc= MIME-Version: 1.0 Received: by 10.216.79.11 with SMTP id h11mr1087240wee.77.1307049753847; Thu, 02 Jun 2011 14:22:33 -0700 (PDT) Received: by 10.216.253.168 with HTTP; Thu, 2 Jun 2011 14:22:33 -0700 (PDT) In-Reply-To: <8377D924-763A-4C44-A018-052A74686BA9@seancoates.com> References: <4DE5368A.6050603@moonspot.net> <0047B798-AFBC-41CF-A4EC-74A026B657FE@seancoates.com> <8377D924-763A-4C44-A018-052A74686BA9@seancoates.com> Date: Thu, 2 Jun 2011 23:22:33 +0200 Message-ID: To: Sean Coates Cc: PHP internals Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] RFC: Short syntax for Arrays (redux) From: pierre.php@gmail.com (Pierre Joye) On Thu, Jun 2, 2011 at 10:19 PM, Sean Coates wrote: >>> If people vote on this now, will further discussion about how this SHOU= LD >>> work be shut down with "we already voted on this"? >> which other discussions do you wish? Json is clearly not an option and >> not enough people (but a couple) likes or wants it. >> >> The RFC is about short array syntax and as far as I can see there is >> already a clear consensus for one of the proposed new syntax. > > I don't see why JSON (or JSON-like, or JavaScript Object Literal, or what= ever the least politically-fired term of the moment) syntax is "clearly" no= t an option. I'm considering writing a new RFC that calls for first-class J= SONishy syntax, but I have better things to do if it's already dead in the = water. > > As much as I'd like to avoid drawing out this discussion, I think a prema= ture vote that will be used as a political wedge to shut down all future sy= ntaxes that don't use T_ARRAY is not in the best interest of PHP. You can still vote -1 on this RFC and try to block it. That's the purpose of the votes. But arguing endlessly why json-like syntax is better without an alternative RFC and patch won't bring you anywhere. Cheers, --=20 Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org