Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:52726 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 58544 invoked from network); 1 Jun 2011 22:52:15 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Jun 2011 22:52:15 -0000 Authentication-Results: pb1.pair.com smtp.mail=dukeofgaming@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=dukeofgaming@gmail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.42 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: dukeofgaming@gmail.com X-Host-Fingerprint: 209.85.218.42 mail-yi0-f42.google.com Received: from [209.85.218.42] ([209.85.218.42:43895] helo=mail-yi0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B7/3A-32367-E92C6ED4 for ; Wed, 01 Jun 2011 18:52:15 -0400 Received: by yib12 with SMTP id 12so155296yib.29 for ; Wed, 01 Jun 2011 15:52:12 -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:from:date :message-id:subject:to:cc:content-type; bh=8cZ9v48Md7OyM/5L9tMlFN8sWC/4a4XENSczZLKC45Y=; b=R3Ol23Br6DuijRCovxAoww2WLCE6vJe6D3HT0VzUaBvyKc5QLTNw7OwCMB2BHbejgJ tHrCua8q5pq1wsN4dpP1VRYT46tkjqWN98dg2vUDuwr3c23HZeB39b6O/xfiCl+t+JOQ dISqXrvnu61sksxrh72xZcxkmrfQw2zHWezp0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=HgSuQOFnJu+Ovtg+bDgfYI7wWS70+MSNFsROEQY069QTR0gc8yybS1ZrRMjWBkwEwL Ralb1oioGiDHvWhXr8fFGY4DtgyxxxrZsLUlSIDYGxzF2sIQStXNtcfjI4BbRZiExcI/ ywYCP4qgoZ8yRtqFRvQUqUQTeasKI31ciyYMU= Received: by 10.101.181.17 with SMTP id i17mr26522anp.65.1306968732225; Wed, 01 Jun 2011 15:52:12 -0700 (PDT) MIME-Version: 1.0 Received: by 10.100.96.15 with HTTP; Wed, 1 Jun 2011 15:51:52 -0700 (PDT) In-Reply-To: References: <4DE5368A.6050603@moonspot.net> <8BEEEE49-8DA3-4634-BF9C-120F7A15B613@roshambo.org> Date: Wed, 1 Jun 2011 17:51:52 -0500 Message-ID: To: Michael Shadle Cc: Sean Coates , Anthony Ferrara , PHP internals Content-Type: multipart/alternative; boundary=001636c92add04526904a4ae5f5d Subject: Re: [PHP-DEV] RFC: Short syntax for Arrays (redux) From: dukeofgaming@gmail.com (dukeofgaming) --001636c92add04526904a4ae5f5d Content-Type: text/plain; charset=ISO-8859-1 I still don't get it, the idea of making it look like json wont make it json, it will be PHP, and if you dare to write you "jsony" object/array with single quoted strings wont break the code even when its not JSON. I'll say it again: not even Javascript supports 100% valid JSON. I'll say it even more times: Not even Javascript supports 100% valid JSON Not even Javascript supports 100% valid JSON Not even Javascript supports 100% valid JSON Not even Javascript supports 100% valid JSON Not even Javascript supports 100% valid JSON JSON even has its own mime type. The idea of JSON as a first-class citizen is a fallacy IMHO. The concept itsel is not ugly, but for god's sake, lets put it in a separate RFC and lets decide con the actual RFC. Perhaps the JSON idea could benefit from autoboxing and a native class?: https://wiki.php.net/rfc/autoboxing JSON is a serializarion format, not a data structure, you coud write an associative array and if PHP knew the way, it could be autointerpreted as JSON, no need to make PHP code look like JSON. I think that the *BEHAVIOR* of arrays/objects as JSON and without the intervention of serialization functions should be in a separate RFC. There is really no point to make PHP *look* like JSON to handle JSON natively . This JSON matter and short array/object syntax are different issues just the way "