ID: 9320
Updated by: stas
Old-Status: Open
Status: Closed
Bug Type: Scripting Engine problem
Assigned To: 

?> is recognized in comments, it's known  - in order to allow:
<some html><?php call_code(); // here we do stuff ?></some html>

Previous Comments:

[2001-02-17 13:32:45] [EMAIL PROTECTED]
Yep, you're right, it should not end with the ?> in a string


[2001-02-17 13:13:01] [EMAIL PROTECTED]
It is bug, bug and bug!!!

See the manual :

| The "one-line" comment styles actually only
| comment to the end of the line or the current
| block of PHP code, whichever comes first.

The thing echoed should not mean the end of
the block: 

1: <?php
2:   #echo "<?php echo 'test'; ?>";
3: ?>

The block starts on line 1 and ends
on line 3. I think we can agree on this.

BUT: the PHP parser thinks that the end of
code is on line 2, but this is just
one thing echoed, and not meant to be
parsed by this PHP parser...

The end of block is on line 3.

This is not documented!


[2001-02-17 13:02:28] [EMAIL PROTECTED]
This is not a bug, but documented behaviour.


[2001-02-17 12:14:46] [EMAIL PROTECTED]
See this code:

  echo "<?php echo 'test'; ?>";

This works good. And prints:
<?php echo 'test'; ?>
which it should print.

Then using a comment:

  #echo "<?php echo 'test'; ?>";

This prints: 



The ?> is recognized in the string, although
it should not be recognized I think!!!

This is a problem if you generate php pages,
as Smarty does for expample... (


ATTENTION! Do NOT reply to this email!
To reply, use the web interface found at

PHP Development Mailing List <>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to