Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:53371 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 59448 invoked from network); 19 Jun 2011 03:05:26 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 19 Jun 2011 03:05:26 -0000 Authentication-Results: pb1.pair.com smtp.mail=dragoonis@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=dragoonis@gmail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.210.170 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: dragoonis@gmail.com X-Host-Fingerprint: 209.85.210.170 mail-iy0-f170.google.com Received: from [209.85.210.170] ([209.85.210.170:43004] helo=mail-iy0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 02/00-59257-4776DFD4 for ; Sat, 18 Jun 2011 23:05:25 -0400 Received: by iym1 with SMTP id 1so1466386iym.29 for ; Sat, 18 Jun 2011 20:05:22 -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=zz7ehX4JBs9okQ0ce5GirmhNY5hOmfsabXvwzwvcdGQ=; b=NS6BEen3zEfTKl7EdFhH09YA1BfUe6t0pNhNN0QPFNv9JYjcFUs4EaYDX1IaXYWL/F avDdTUVnPzvUPjotr/dS/GMcfwZWa3vgFVpkI90SlltM3Ivn47kUgCgCjhToh9qHNBBI EZUaWqT07sD6mv0Z2v4hgJ9dri67Mi6gtjB+g= 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=v2/VnGMZOw7ouvgymuDno2LGL9lQN/2a2BZ3B+BMqoTrwU0xjfxzCexFGQ27NRnoyx mkppf2uxDr9LoG5zbSs8LfdY/AQf157ZLwWaiu25YmLgdkMHJaRR4qT1cWCBGvdQaksA k7EMIJSjKKD8RibFsLR3lRQLwTq4aWYpc9mV8= MIME-Version: 1.0 Received: by 10.42.178.68 with SMTP id bl4mr4315799icb.343.1308452721891; Sat, 18 Jun 2011 20:05:21 -0700 (PDT) Received: by 10.42.108.70 with HTTP; Sat, 18 Jun 2011 20:05:21 -0700 (PDT) In-Reply-To: <20110619025655.GA14388@panix.com> References: <084D2F1E-87E7-44CF-B8B6-47A250AD928D@seancoates.com> <20110619025655.GA14388@panix.com> Date: Sun, 19 Jun 2011 04:05:21 +0100 Message-ID: To: PHP Internals List Cc: Daniel Convissor Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] Object and Array Literals From: dragoonis@gmail.com (Paul Dragoonis) On Sun, Jun 19, 2011 at 3:56 AM, Daniel Convissor wrote: > Hi: > > I wasn't keen on earlier proposals for the [] array syntax. =A0Sean, your > case is laid out in a clear manner and addresses my concerns. =A0I like > this RFC. > > >> =A0 =A0 =A0 * Strictness of unquoted keys. > > Keys should be quoted. =A0At the very least, unquoted keys should raise a= n > E_NOTICE. > > >> =A0 =A0 =A0 * Support =3D> in addition to : as a key:value separator. > > I guess. > > >> =A0 =A0 =A0 * possibility of simply not supporting the \u### syntax for = Unicode >> =A0 characters in literal strings (just like the rest of PHP). > > It'd be nice to have, but not essential. > > >> =A0 =A0 =A0 * Should mixed-format (numeric and associative arrays) be al= lowed? >> =A0 =A0 =A0 (e.g. [1,'two':2, 3]) > > Yes, just like JSON (kind of) and PHP support. I +1 the JSON syntax for keys on objects and arrays. Specifically I mean quoting the keys, this will remove ambiguity if it was supposed to use a constant or whatnot. String quoted keys++ > > Thanks, > > --Dan > > -- > =A0T H E =A0 A N A L Y S I S =A0 A N D =A0 S O L U T I O N S =A0 C O M P = A N Y > =A0 =A0 =A0 =A0 =A0 =A0data intensive web and database programming > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0http://www.AnalysisAndSolutions.com/ > =A04015 7th Ave #4, Brooklyn NY 11232 =A0v: 718-854-0335 f: 718-854-0409 > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >