From my experience the PHP parser acts much like the HTML parser in the 
fact that it doesn't give a damn about carriage returns....

ed

At 03:01 PM 5/28/2002 -0600, Kevin Stone wrote:
>Exactly.. it doesn't seem to make any sense.  Esspecially since it's such as
>absolutely incredibly undeniably easy thing to check for.  :)  If the code
>doesn't end with an uncommented ?> then just parse the code as text.  That's
>what it does anyway so why catch commented code at all?
>
>----- Original Message -----
>From: "Johnson, Kirk" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Sent: Tuesday, May 28, 2002 2:55 PM
>Subject: RE: [PHP] comment followed by ?> fails to parse
>
>
> > Which begs the question, why does PHP see a '?>' in a '//' comment line,
>but
> > not in a multi-line comment, e.g., /* ?> */ ?
> >
> > > -----Original Message-----
> > > From: Ed Gorski [mailto:[EMAIL PROTECTED]]
> > > Sent: Tuesday, May 28, 2002 2:46 PM
> > > To: Leotta Natalie (NCI/IMS); 'Jonathan Rosenberg'; Johnson, Kirk;
> > > [EMAIL PROTECTED]
> > > Subject: RE: [PHP] comment followed by ?> fails to parse
> > >
> > >
> > > No the parser sees the ?> after a // because it needs to see
> > > when to quit
> > > out (unlike traditional, compiled languages) but it won't
> > > have this same
> > > effect in a string literal.....
> > >
> > > ed
> >
> > --
> > 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


-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to