#10311 [Com]: parse error generated for comment
| From: | pussy-wet962 at hotmail dot com | Date: | Tue, 20 Jul 2004 15:00:43 +0000 |
| Subject: | #10311 [Com]: parse error generated for comment | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-62786@lists.php.net to get a copy of this message | ||
ID: 10311
Comment by: pussy-wet962 at hotmail dot com
Reported By: slyder at earendel dot org
Status: Bogus
Bug Type: Scripting Engine problem
Operating System: Solaris 5.7
PHP Version: 4.0.4pl1
New Comment:
<a href=http://jpink-buthblowjob-t.da.ru>pussy
wet</a>
Previous Comments:
------------------------------------------------------------------------
[2001-04-12 16:15:30] cnewbill@php.net
This is expected behavior. Not a bug.
The part of the expression that is causing the problem is ?>. Try just
having // ?>, it will do the same thing. PHP interprets this as the end
of the code block.
An example of why this is so:
<?php print $value; // print value ?>
-Chris
------------------------------------------------------------------------
[2001-04-12 15:50:12] slyder at earendel dot org
//$line = preg_replace("/<?[ _0-9A-Za-z\$\?\&\"\=;]+QBUYURLQ[
_0-9A-Za-z\$\?\&\"\=;]+?>/", $buyurl, $line);
ok pretend thats all one line. the problem is that when using c++ style
comments, I get a parse error @ line [length of file + 1]. using c style
comments makes it go away. the point of the code it was to replace the
php part of a line that contained QBUYURLQ in it w/ just the url. it's
no longer needed, but took a while to figure out that a comment was
generating a parse error :)
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=10311&edit=1