Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:20774 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 93627 invoked by uid 1010); 28 Nov 2005 20:27:51 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 93612 invoked from network); 28 Nov 2005 20:27:51 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 Nov 2005 20:27:51 -0000 X-Host-Fingerprint: 81.68.134.212 c514486d4.cable.wanadoo.nl Received: from ([81.68.134.212:12395] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id B2/3F-21657-6486B834 for ; Mon, 28 Nov 2005 15:27:50 -0500 Message-ID: To: internals@lists.php.net References: <1607285441.20051127115816@marcus-boerger.de><20051127212028.GA12580@panix.com> <200511272232.53858.johannes@php.net><1133127650.9056.48.camel@localhost.localdomain><00bc01c5f3a5$2155c630$7d051fac@stumpy> <438AC658.6010405@gmail.com> <793837231.20051128202942@marcus-boerger.de> Date: Mon, 28 Nov 2005 21:15:47 +0100 Lines: 56 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Posted-By: 81.68.134.212 Subject: Re: [PHP-DEV] wrote in message news:793837231.20051128202942@marcus-boerger.de... > Hello Bastian, > > id like to see ' > marcus > > Monday, November 28, 2005, 9:56:56 AM, you wrote: > > > What concerns me most is that > tags will be disabled or not in php6. I currently use <%= to counter > > this, but I am most certainly *not* happy with it. > > > So a clean > about xml/xsl files parsed and neither about my templates growing too > > large because of php overhead. > > > Sara Golemon wrote: > >>> I recall this being discussed before, but not what came of it: is there > >>> a problem with just ignoring >>> or =? >>> much doubt there's any BC break. Unless someone's program relies on > >>> parse errors. > >>> > >> The problem there becomes legacy support for: > >> > >> > >> > >> And before you say "just watch for parens" there's also: > >> > >> > >> > >> and a much more insiduous example: > >> > >> > >> > >> no semicolon, no parens, no paamayim nekudotayim, nothing but a > >> perfectly valid looking PI tag. > >> > >> -Sara > > > > > Best regards, > Marcus