-Original Message-
> From: Thalis A. Kalfigopoulos [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, May 29, 2002 1:40 PM
> To: Jonathan Rosenberg
> Cc: [EMAIL PROTECTED]
> Subject: RE: [PHP] comment followed by ?> fails to parse
> On Wed, 29 May 2002, Jonathan Rosenberg
On Wed, 29 May 2002, Jonathan Rosenberg wrote:
> -Original Message-
> > From: Thalis A. Kalfigopoulos [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, May 29, 2002 10:27 AM
> > To: [EMAIL PROTECTED]
> > Subject: Re: [PHP] comment followed by ?> fails to pa
-Original Message-
> From: Thalis A. Kalfigopoulos [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, May 29, 2002 10:27 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [PHP] comment followed by ?> fails to parse
> On Wed, 29 May 2002, Jason Wong wrote:
> > Yes this hightli
On Wed, 29 May 2002, Jason Wong wrote:
> On Wednesday 29 May 2002 21:27, Leotta, Natalie (NCI/IMS) wrote:
> > I disagree. I use // because then when I need to take out a chunk of code
> > (the requirements for the programs change faster than I can keep up with
> > them!!) I can do /* unnecessary
On Wed, 29 May 2002, Ford, Mike [LSS] wrote:
> > -Original Message-
> > From: Thalis A. Kalfigopoulos [mailto:[EMAIL PROTECTED]]
> > Sent: 28 May 2002 20:21
> >
> > If I write a comment line with // and I include in it ?> then
> > it fails to parse the rest of the page bec
On Wednesday 29 May 2002 21:27, Leotta, Natalie (NCI/IMS) wrote:
> I disagree. I use // because then when I need to take out a chunk of code
> (the requirements for the programs change faster than I can keep up with
> them!!) I can do /* unnecessary code */ and it doesn't end prematurely.
Yes th
EMAIL PROTECTED]]
Sent: Wednesday, May 29, 2002 9:25 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: [PHP] comment followed by ?> fails to parse
Bah quit complaining, you should be using /* comments */ anyway.
ed
At 09:16 PM 5/29/2002 +0800, Jason Wong wrote:
>On Wednesday 29 May
Bah quit complaining, you should be using /* comments */ anyway.
ed
At 09:16 PM 5/29/2002 +0800, Jason Wong wrote:
>On Wednesday 29 May 2002 21:10, Brinkman, Theodore wrote:
> > It really should ignore anything in any sort of comment. The whole point
> > of a comment is that it provides the
On Wednesday 29 May 2002 21:10, Brinkman, Theodore wrote:
> It really should ignore anything in any sort of comment. The whole point
> of a comment is that it provides the programmer with information and is
> ignored by the compiler/interpreter. If // is supposed to comment until
> the end of th
wed by ?> fails to parse
Hrm.. that's possible. I'm running v4.12
-Kevin
- Original Message -
From: "Ed Gorski" <[EMAIL PROTECTED]>
To: "Kevin Stone" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Tuesday, May 28, 2002 3:01 PM
Subject: Re
[snip]
...lots of stuff from lots of messages...
[/snip]
If you need to display PHP code in an HTML page and have it validate
properly you need to use the following;
which will properly display as
As a matter of course it is typical to use < (<) and > (>) along with
a set of pre-form
> -Original Message-
> From: Ed Gorski [mailto:[EMAIL PROTECTED]]
> Sent: 28 May 2002 21:53
>
> 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 fi
> -Original Message-
> From: Thalis A. Kalfigopoulos [mailto:[EMAIL PROTECTED]]
> Sent: 28 May 2002 20:21
>
> 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.
world";
?>
-Kevin
- Original Message -
From: "Jason Wong" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, May 28, 2002 3:14 PM
Subject: Re: [PHP] comment followed by ?> fails to parse
> On Wednesday 29 May 2002 05:03, Kevin Stone wrote:
>
On Wednesday 29 May 2002 05:03, Kevin Stone wrote:
> Hrm.. that's possible. I'm running v4.12
Works fine on v4.0.6
--
Jason Wong -> Gremlins Associates -> www.gremlins.com.hk
Open Source Software Systems Integrators
* Web Design & Hosting * Internet & Intranet Applications Development *
/*
Th
gt;for us ;)
>
>Kirk
>
> > -Original Message-
> > From: Ed Gorski [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, May 28, 2002 3:04 PM
> > To: Kevin Stone; [EMAIL PROTECTED]
> > Subject: Re: [PHP] comment followed by ?> fails to parse
> >
> >
Kevin Stone; [EMAIL PROTECTED]
> Subject: Re: [PHP] comment followed by ?> fails to parse
>
>
> 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
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
> > no
gt;
> >// reg ex.. legal
> >ereg('?>', $tmp);
> >
> >// Comment.. illegal. Why? Makes no sense.
> >/*?>*/
> >
> >-Kevin
> >
> >
> >----- Original Message -
> >From: "Jonathan Rosenberg" <[EMAIL PROT
Hrm.. that's possible. I'm running v4.12
-Kevin
- Original Message -
From: "Ed Gorski" <[EMAIL PROTECTED]>
To: "Kevin Stone" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Tuesday, May 28, 2002 3:01 PM
Subject: Re: [PHP] comment followed
gt; >To: "Johnson, Kirk" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> > >Sent: Tuesday, May 28, 2002 2:46 PM
> > >Subject: RE: [PHP] comment followed by ?> fails to parse
> > >
> > >
> > > > BTW: if my last message was correc
h 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 '?>'
CI/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
L PROTECTED]>; "Johnson Kirk" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Tuesday, May 28, 2002 2:52 PM
Subject: Re: [PHP] comment followed by ?> fails to parse
> No, if you use /* ? */ as a comment the parser will skip right over
> it.if you want to use s
- Original Message -
>From: "Jonathan Rosenberg" <[EMAIL PROTECTED]>
>To: "Johnson, Kirk" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
>Sent: Tuesday, May 28, 2002 2:46 PM
>Subject: RE: [PHP] comment followed by ?> fails to parse
>
>
> > BT
berg'; Johnson, Kirk;
> [EMAIL PROTECTED]
> Subject: RE: [PHP] comment followed by ?> fails to parse
>
>
> But why wouldn't the parser skip right over a // line?
> it shouldn't even
> see anything in it.
>
> -Original Message-
> From: Jonathan R
>*/
-Kevin
- Original Message -
From: "Jonathan Rosenberg" <[EMAIL PROTECTED]>
To: "Johnson, Kirk" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Tuesday, May 28, 2002 2:46 PM
Subject: RE: [PHP] comment followed by ?> fails to parse
> BTW: if my l
That makes sense. Thanks!
-Natalie
-Original Message-
From: Ed Gorski [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 28, 2002 4:46 PM
To: Leotta, Natalie (NCI/IMS); 'Jonathan Rosenberg'; Johnson Kirk;
[EMAIL PROTECTED]
Subject: RE: [PHP] comment followed by ?> fails to p
kip right over a // line? it shouldn't even
>see anything in it.
>
>-Original Message-
>From: Jonathan Rosenberg [mailto:[EMAIL PROTECTED]]
>Sent: Tuesday, May 28, 2002 4:46 PM
>To: Johnson, Kirk; [EMAIL PROTECTED]
>Subject: RE: [PHP] comment followed by ?> fa
But why wouldn't the parser skip right over a // line? it shouldn't even
see anything in it.
-Original Message-
From: Jonathan Rosenberg [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 28, 2002 4:46 PM
To: Johnson, Kirk; [EMAIL PROTECTED]
Subject: RE: [PHP] comment followed b
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
>
nt: 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 encoun
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:
33 matches
Mail list logo
