Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:15300
Return-Path: <helly@php.net>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 30202 invoked by uid 1010); 7 Mar 2005 18:40:03 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 30184 invoked from network); 7 Mar 2005 18:40:03 -0000
Received: from unknown (HELO php.net) (127.0.0.1)
  by localhost with SMTP; 7 Mar 2005 18:40:02 -0000
X-Host-Fingerprint: 81.169.182.136 h59705.serverkompetenz.net Linux 2.4/2.6
Received: from ([81.169.182.136:46994] helo=strato.aixcept.de)
	by pb1.pair.com (ecelerity HEAD r(5124)) with SMTP
	id 9C/07-53294-200AC224 for <internals@lists.php.net>; Mon, 07 Mar 2005 13:40:02 -0500
Received: from [192.168.1.3] (dsl-082-083-244-202.arcor-ip.net [82.83.244.202])
	(using TLSv1 with cipher AES256-SHA (256/256 bits))
	(No client certificate requested)
	by strato.aixcept.de (Postfix) with ESMTP id 52DB235C1D6;
	Mon,  7 Mar 2005 19:43:02 +0100 (CET)
Date: Mon, 7 Mar 2005 19:38:06 +0100
Reply-To: Marcus Boerger <helly@php.net>
X-Priority: 3 (Normal)
Message-ID: <1931340839.20050307193806@marcus-boerger.de>
To: Zeev Suraski <zeev@zend.com>
Cc: internals <internals@lists.php.net>
In-Reply-To: <5.1.0.14.2.20050307160739.0aeb3390@localhost>
References: <5.1.0.14.2.20050307160739.0aeb3390@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Problem with fix for bug #31672
From: helly@php.net (Marcus Boerger)

Hello Zeev,

 i do not think this is a good excuse for ignoring xml compliance.

marcus

Monday, March 7, 2005, 3:10:57 PM, you wrote:

> Guys,

> I'd like to revert the fix for bug #31672 ("</script> is not considered 
> closing tag if preceded by one-line comment").  While theoretically 
> correct, I'd rather resolve it by fixing the docs.

> The reason is simple - unlike ?> and %>, the string "</script>" is very 
> much likely to appear inside one line comments:

> // print "<script>foo</script>";

> That suddenly fails.  That's probably the reason we didn't implement it in
> the first place.

> Any objections to reverting this fix?

> Zeev




-- 
Best regards,
 Marcus                            mailto:helly@php.net