The only situation I can think of where this would happen is

<?php // print "stuff"; ?>

i.e. one liners

If this is your case this is expected behavior IIRC.  Otherwsie submit a small script that reproduces the problem.

-Chris

Okay it would happen on more than one liners.

basically if you have a ?> on the same line as the // comment it will do this.

I know there is some other bugs on this same problem, but I don't have the numbers handy.

-Chris

unable to reproduce on RH Linux 7.

This sounds very bogus.

I received an email stating that it could not be reproduced 
on a  RH Linux 7 machine.  This problem is specific to Mac 
OS X client, so I'm sure that you were unable to reproduce 
it on your box.

Either way, this is definately happening and is not "bogus" 
as you said.

Also in reply to the other suggestions regarding one liners 
vs multiple line comments:

The lines I have commented are all on their own line and 
are one liners.  More or less, anywhere I use a "//" to 
comment, the entire line is displayed to the user.  The 
following two scripts will give me the same result.

<?php
    // This comment will show on the web page
?>

<?php
    print('// This comment will show on the web page');
?>

I noticed in the documentation that the "//" was considered 
a C++ style of commenting.  Do I possibly need a particular 
module or directive to say that "//" is a comment?

Thanks,
Lael

For those asking for an example of the script and the 
output.

Using the following:
<code>
<?php
    print("Working so far <BR>");
    print("Still working next line is going to be a 
comment<BR>");
    // This line should be a comment
    print("This is the next line past the comment<BR>");
?>
</code>

I get the following result:
<browser output>
// This line should be a comment print("This is the next 
line past the comment
"); Working so far 
Still working next line is going to be a comment
<end of browser output>

Thanking everyone for the help.  Greatly appreciate it.

Lael

could you please check the source of the output (View -> Page Source in Netscape 4.x, and View -> Source in IE) to check that PHP scripts get actually executed?

(Sorry if this is dumb, but the example you provided really looks like this is the case.)

The ## works just the same as the //

Also, for those that asked I try it in Netscape.  Netscape 
does the same thing.  The php is being processed, it's just 
that any line with a "//" or a "##" will first be displayed 
up at the top of the page and then from the line after the 
comment the PHP will resume.

status: open

As asked before by Cynic, can you view the source of the output of the PHP-file? It doesn't matter which browser you use. See the post of Cynic for instructions on doing this with IE or Netscape ;)

status->feedback

No feedback. Closing.