Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:20163 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 65754 invoked by uid 1010); 18 Nov 2005 16:09:12 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 65739 invoked from network); 18 Nov 2005 16:09:12 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Nov 2005 16:09:12 -0000 X-Host-Fingerprint: 206.190.38.116 web50807.mail.yahoo.com FreeBSD 4.7-5.2 (or MacOS X 10.2-10.3) (2) Received: from ([206.190.38.116:36057] helo=web50807.mail.yahoo.com) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 1D/1E-07637-6ACFD734 for ; Fri, 18 Nov 2005 11:09:10 -0500 Received: (qmail 19390 invoked by uid 60001); 18 Nov 2005 16:09:07 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=ZIsDgdz8wT714jzmaXDYZ5u5M3D41s5I3e/DNFuOodXOVN3f3pKGQvc78SLS9L+gJszDN1OsTRBG54clNkSneepl5XFIIbUznuQYuXTAsOD9WubOXpcja/RQ1ky9uDwhV3g4q50d1wOqbP5Cr6ZaH2eRYMK9TF9RxuwSW98MJVs= ; Message-ID: <20051118160907.19388.qmail@web50807.mail.yahoo.com> Received: from [64.231.132.164] by web50807.mail.yahoo.com via HTTP; Fri, 18 Nov 2005 08:09:07 PST Date: Fri, 18 Nov 2005 08:09:07 -0800 (PST) To: internals@lists.php.net MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: Re: dropping curly braces From: jayboots@yahoo.com (boots) Hi. Is there really a good reason to drop {} string access? Does it make the engine better? Are you going to use {} for something else? If not, then wouldn't it make logical sense to do what was documented and drop the [] syntax? Sure, I've read the argument that [] is used in other languages but as we all know, PHP != (insert language) so that is not really valid. I've read the argument that [] "makes more sense" but obviously it has long ago been decided and documented otherwise. I've read that dropping [] will break apps -- but that is equally true for {}. There seems to be no reason for this other than whim and that leaves a sour taste. Yes, we will update our codebases (thanks for the extra and pointless work, btw) but not to [] for string access but rather substr() which I hope is safer long-term. Future proofing is getting much harder because now we can't even rely on documented behaviours and existing deprecation notices. Some people will say, "Oh, it is safe to use [] so don't worry" but it seems that these same people said that about {}. If this makes PHP better in some way I could see the need but as it is, it seems like a pity to me. Best. __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com