Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:52713 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 34371 invoked from network); 1 Jun 2011 22:14:25 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Jun 2011 22:14:25 -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 74.125.82.170 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: 74.125.82.170 mail-wy0-f170.google.com Received: from [74.125.82.170] ([74.125.82.170:44714] helo=mail-wy0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 19/55-32367-FB9B6ED4 for ; Wed, 01 Jun 2011 18:14:24 -0400 Received: by wyb34 with SMTP id 34so219242wyb.29 for ; Wed, 01 Jun 2011 15:14:20 -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=zIlVypsmPpdv2XIvgyHINjRt5mdKCTt8dO18IzOzSkg=; b=Vd2gKM02Y3ilAl2GCK0Ufs+j3otR96c4Bfa4ze9P9+JYOW5jof8kWBQ4yWEotwp02k sSQD4U8QvNe9K86yAIIqn9eg+PIjl5UYMLsdOiQgm8rCv+l5WJQjQsLwuOn4oD0q4Bh4 HUoqqL4lONfCjmmUDZ4PkBRUPKZPRYtDd6p4w= 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=Poy8foZJwBxzZZQXpJ4Sm56vb+oIn/iuWkhDKcloKd+me0Ma5asA0YzJRHD7Bja/Ku hnfaAd1O1EKfDr7MbaY4u/SveBS0+hPJVko0i+3mDOpDjiW8k+Xe9WK5vQOWXmC3Guba lUq70rAKRVuHLlGATSG3BXPgO8692e311y7aw= MIME-Version: 1.0 Received: by 10.216.233.211 with SMTP id p61mr2895769weq.107.1306966460187; Wed, 01 Jun 2011 15:14:20 -0700 (PDT) Received: by 10.216.253.168 with HTTP; Wed, 1 Jun 2011 15:14:19 -0700 (PDT) In-Reply-To: References: <4DE5368A.6050603@moonspot.net> <8BEEEE49-8DA3-4634-BF9C-120F7A15B613@roshambo.org> Date: Thu, 2 Jun 2011 00:14:19 +0200 Message-ID: To: John Crenshaw 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 Wed, Jun 1, 2011 at 11:59 PM, John Crenshaw w= rote: > Spot on. It has nothing to do with extra typing (and that sort of design = is part of what ruined Ruby). My fingers move plenty fast and if extra char= acters make things more safe or more readable, I'll be the first to sign up= . In this case, however, the extra characters just make things messy. > 1. The most readable format is pure JSON > 2. The most familiar format is pure JSON (because these same developers a= re almost certainly already using it in their jQuery code) > 3. The most compact format is pure JSON > 4. The format most consistent with other languages is JSON Not sure which other language you refer to but python, C, perl (using () instead) uses a very similar format. To me using json (a serializer format) in code sounds wrong, very wrong, in the 1st place. What's the next step? Bson? Using JSON in the code also won't save anyone from any kind of conversions errors from or to JSON. This RFC proposed two syntaxes, which can be later extended to object as well if desired. I would stronlgy suggest to focus on this RFC and get it sort out (accepted or rejected). If it requires to clarify the RFC to make the voting easier, then let do it. Cheers, --=20 Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org