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:[EMAIL PROTECTED]] > Sent: Tuesday, May 28, 2002 4:08 PM > To: [EMAIL PROTECTED] > 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 > > > -----Original Message----- > > From: Thalis A. Kalfigopoulos [mailto:[EMAIL PROTECTED]] > > Sent: Tuesday, May 28, 2002 1:21 PM > > To: [EMAIL PROTECTED] > > Subject: [PHP] comment followed by ?> fails to parse > > > > > > If I write a comment line with // and I include in > it ?> then > > it fails to parse the rest of the page because (i'm > guessing) > > 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 > > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
