Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:20146 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 67290 invoked by uid 1010); 18 Nov 2005 13:27:30 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 67275 invoked from network); 18 Nov 2005 13:27:30 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Nov 2005 13:27:30 -0000 X-Host-Fingerprint: 66.249.82.195 xproxy.gmail.com Linux 2.4/2.6 Received: from ([66.249.82.195:17295] helo=xproxy.gmail.com) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 92/10-07637-2C6DD734 for ; Fri, 18 Nov 2005 08:27:30 -0500 Received: by xproxy.gmail.com with SMTP id s19so161703wxc for ; Fri, 18 Nov 2005 05:27:27 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=c7R7j6gSt74LtZsDxM8HLELsF7eNu5v0LqeKo0NIdzQj55U61O2tbcWOR1X5fwIyO5Qe2QeGeTSWefsKlhkpAHkKNHq0//UJKP2XwxMNuRChblIXI2ZumcSzZNHpFjL5tneiZBmdBvLSqjS4sHiMfyw8cjOvSJV8HG/hnPgvbKw= Received: by 10.65.191.13 with SMTP id t13mr912983qbp; Fri, 18 Nov 2005 05:27:27 -0800 (PST) Received: by 10.65.186.4 with HTTP; Fri, 18 Nov 2005 05:27:26 -0800 (PST) Message-ID: Date: Fri, 18 Nov 2005 15:27:26 +0200 To: internals@lists.php.net In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: Subject: Re: [PHP-DEV] dropping curly braces From: manchokapitancho@gmail.com (Marian Kostadinov) +1 for keeping {} sintax in PHP6. It's not fair for all those people who endeavoured to write a good PHP code and followed the recommendations for it. And why should this feature be removed while in the mean time PHP developers are desparately keeping some very very old stuff for BC reasons? This is IMO an inconsistent behaviour. On 18/11/05, Ford, Mike wrote: > So all of those who belived the "[] for string access is deprecated" line= (or simply prefer the visual differentiation) and have 10s of thousands of= lines of code with liberal use of $string{} are going to have to spend age= s fixing that up? > > > Having two syntaxes for the same thing makes no sense, > >