Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:20116 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 80170 invoked by uid 1010); 18 Nov 2005 00:05:16 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 80155 invoked from network); 18 Nov 2005 00:05:16 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Nov 2005 00:05:16 -0000 X-Host-Fingerprint: 204.11.219.139 lerdorf.com Linux 2.4/2.6 Received: from ([204.11.219.139:52123] helo=colo.lerdorf.com) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 95/BC-07637-BBA1D734 for ; Thu, 17 Nov 2005 19:05:16 -0500 Received: from [207.126.233.18] (rasmus2.corp.yahoo.com [207.126.233.18]) (authenticated bits=0) by colo.lerdorf.com (8.13.5/8.13.5/Debian-3) with ESMTP id jAI057OE013230 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 17 Nov 2005 16:05:07 -0800 Message-ID: <437D1AB2.6080908@lerdorf.com> Date: Thu, 17 Nov 2005 16:05:06 -0800 User-Agent: Thunderbird 1.5 (Macintosh/20051025) MIME-Version: 1.0 To: Robert Cummings CC: Ilia Alshanetsky , Andreas Korthaus , internals@lists.php.net References: <437B530A.5050105@prohost.org> <437CF6B4.5080207@web.de> <437CF943.7090800@lerdorf.com> <437D0D08.8060805@web.de> <437D0E22.7080006@lerdorf.com> <437D11B7.7090102@web.de> <437D1361.5080504@prohost.org> <1132271500.18353.53.camel@blobule.suds> In-Reply-To: <1132271500.18353.53.camel@blobule.suds> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] dropping curly braces From: rasmus@lerdorf.com (Rasmus Lerdorf) Robert Cummings wrote: > On Thu, 2005-11-17 at 18:33, Ilia Alshanetsky wrote: >> Andreas Korthaus wrote: >>> OK, but by dropping {} for strings you also remove the possibility to >>> have a convention like "[] for arrays and {} for strings". >>> If I could decide I would drop {} for arrays and [] for strings, but I >>> fear I will not be asked to decide... ;-) >> You may think that {} and [] are different, but in reality same code >> deals with both. Having two constructs for the same behavior is silly >> and leads to confusing, hard to read code. Especially so when you >> consider the fact {} has another meaning that is completely different. > > That should have been considered before everyone was told that [] was > deprecated for strings in favour of {}. Right, that was a mistake which we are fixing now. Removing [] doesn't seem to be a viable option, so rather than continue to tell people to stop using [] since it is never going to go away, the main decision here was to undeprecate []. Whether we will eventually remove {} or not remains to be seen. The initial idea was to try to remove it in PHP6 and in order to help people easily find where these are used, add an E_STRICT for it in PHP 5.1. -Rasmus