Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:20208 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 62522 invoked by uid 1010); 20 Nov 2005 22:28:10 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 62507 invoked from network); 20 Nov 2005 22:28:10 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 Nov 2005 22:28:10 -0000 X-Host-Fingerprint: 80.249.110.212 xian.ncuk.net Linux 2.5 (sometimes 2.4) (4) Received: from ([80.249.110.212:58719] helo=xian.ncuk.net) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 71/61-11378-978F0834 for ; Sun, 20 Nov 2005 17:28:09 -0500 To: internals@lists.php.net Date: Sun, 20 Nov 2005 22:27:57 +0000 User-Agent: KMail/1.9 Cc: Christian Schneider References: <00A2E2156BEE8446A81C8881AE117F192C1BB0@companyweb> <4380F6CD.2080203@cschneid.com> In-Reply-To: <4380F6CD.2080203@cschneid.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1679944.BFxx8BcWy0"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-ID: <200511202228.01891.pookey@pookey.co.uk> Subject: Re: AW: AW: [PHP-DEV] dropping curly braces From: pookey@pookey.co.uk ("Ian P. Christian") --nextPart1679944.BFxx8BcWy0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sunday 20 November 2005 22:21, Christian Schneider wrote: > I second that as people on the list here are undecided about the removal > of {} for strings. Keeping that warning creates even more confusion > about a really minor issue (having two ways of accesing strings offsets). Whilst I'm not really in favour of the change, I think that a change in PHP= =20 like this would be far better accepted were it better documented. The previous major change in PHP got PHP a lot of press, but I didn't read= =20 anywhere an 'official' document as to why things were changed, explaining i= n=20 idiot-terms how to fix things, and why the fix was needed. If this change included a simple sed command that could be applied to code = to=20 fix 'legacy' code, and a page was put up linked form PHP.net's front page t= o=20 the documenation explaining why the change took place, then this change wou= ld=20 be far easier for php users to accept. BTW, whilst on the topic, was there a document written about why the former= =20 mentioned change was made? All I've seen is PHP developers getting stresse= d=20 and saying 'it was a needed fix', with very little justification. =20 Regards, =2D-=20 Ian P. Christian ~ http://pookey.co.uk --nextPart1679944.BFxx8BcWy0 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQBDgPhx6jsuvK/fgkoRAhm1AKC+QsXgw85fNV3NXndNTvZ+20QT0wCcDFer qBvyTu+bGCNnolGM2taOVl4= =mnzI -----END PGP SIGNATURE----- --nextPart1679944.BFxx8BcWy0--