Re: comment followed by ?> fails to parse
| From: | Ed Gorski | Date: | Tue, 28 May 2002 20:52:46 +0000 |
| Subject: | Re: comment followed by ?> fails to parse | ||
| References: | 1 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-99559@lists.php.net to get a copy of this message | ||
No, if you use /* ? */ as a comment the parser will skip right over it.....if you want to use sample code in your script just use:
/*
<?
code here....
?>
*/
that'll work fine
ed
At 02:48 PM 5/28/2002 -0600, Kevin Stone wrote:
I've run into this before as well. Pain in the ass when you want to put example code in your header. It's gotta be a deisgn flaw. // literal.. legal $tmp = '?>'; // reg ex.. legal ereg('?>', $tmp); // Comment.. illegal. Why? Makes no sense. /*?>*/ -Kevin ----- Original Message ----- From: "Jonathan Rosenberg" <jr@tabbysplace.org> To: "Johnson, Kirk" <kjohnson@zootweb.com>; <php-general@lists.php.net> Sent: Tuesday, May 28, 2002 2:46 PM Subject: RE: [PHP] comment followed by ?> fails to parse BTW: if my last message was correct, this means that an occurrence of ?> embedded in a string literal will also cause problems.-----Original Message----- From: Johnson, Kirk [mailto:kjohnson@zootweb.com] Sent: Tuesday, May 28, 2002 4:08 PM To: php-general@lists.php.net Subject: RE: [PHP] comment followed by ?> fails to parse I have wondered for some time if this is a bug or just an interesting design choice ;) I agree with you, I was surprised when I first encountered this. But it is what it is, so code accordingly. Kirk-- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php-----Original Message----- From: Thalis A. Kalfigopoulos [mailto:thalis@cs.pitt.edu] Sent: Tuesday, May 28, 2002 1:21 PM To: php-general@lists.php.net Subject: [PHP] comment followed by ?> fails to parse If I write a comment line with // and I include init ?> thenit fails to parse the rest of the page because (i'mguessing)the parser gets confused and goes off PHP mode. Is this normal? Shouldn't I be able to write literally ANYTHING on a comment line? Sample Code: <? //bla bla ?> $var=1; ?> Output: $var=1; ?> cheers, thalis-- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php