Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:20749 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 49124 invoked by uid 1010); 28 Nov 2005 19:31:36 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 49104 invoked from network); 28 Nov 2005 19:31:36 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 Nov 2005 19:31:36 -0000 X-Host-Fingerprint: 81.169.182.136 ajaxatwork.net Linux 2.4/2.6 Received: from ([81.169.182.136:59762] helo=strato.aixcept.de) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id A5/68-21657-61B5B834 for ; Mon, 28 Nov 2005 14:31:35 -0500 Received: from [192.168.1.3] (dslb-084-063-023-175.pools.arcor-ip.net [84.63.23.175]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by strato.aixcept.de (Postfix) with ESMTP id E3B00610282; Mon, 28 Nov 2005 20:38:01 +0100 (CET) Date: Mon, 28 Nov 2005 20:29:42 +0100 Reply-To: Marcus Boerger X-Priority: 3 (Normal) Message-ID: <793837231.20051128202942@marcus-boerger.de> To: Bastian Grupe Cc: Sara Golemon , internals@lists.php.net In-Reply-To: <438AC658.6010405@gmail.com> 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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] 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