[PHP-DEV] Bug #12323 Updated: // comment tag does not work
ID: 12323 Updated by: lobbin Reported By: [EMAIL PROTECTED] Old Status: Feedback Status: Closed Bug Type: Output Control Operating System: Mac OS X PHP Version: 4.0.6 New Comment: No feedback. Closing. Previous Comments: [2001-12-06 14:11:51] [EMAIL PROTECTED] status-feedback [2001-12-06 14:11:37] [EMAIL PROTECTED] 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 ;) [2001-07-27 13:01:35] [EMAIL PROTECTED] status: open [2001-07-25 11:40:51] [EMAIL PROTECTED] 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. [2001-07-25 02:10:02] [EMAIL PROTECTED] 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 remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/?id=12323 Edit this bug report at http://bugs.php.net/?id=12323edit=1 -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] Bug #12323 Updated: // comment tag does not work
ID: 12323
Updated by: sander
Reported By: [EMAIL PROTECTED]
Status: Open
Bug Type: Output Control
Operating System: Mac OS X
PHP Version: 4.0.6
New Comment:
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 ;)
Previous Comments:
[2001-07-27 13:01:35] [EMAIL PROTECTED]
status: open
[2001-07-25 11:40:51] [EMAIL PROTECTED]
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.
[2001-07-25 02:10:02] [EMAIL PROTECTED]
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.)
[2001-07-24 15:40:01] [EMAIL PROTECTED]
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
commentBR);
// This line should be a comment
print(This is the next line past the commentBR);
?
/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
[2001-07-24 14:28:59] [EMAIL PROTECTED]
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
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/?id=12323
Edit this bug report at http://bugs.php.net/?id=12323edit=1
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] Bug #12323 Updated: // comment tag does not work
ID: 12323 Updated by: sander Reported By: [EMAIL PROTECTED] Old Status: Open Status: Feedback Bug Type: Output Control Operating System: Mac OS X PHP Version: 4.0.6 New Comment: status-feedback Previous Comments: [2001-12-06 14:11:37] [EMAIL PROTECTED] 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 ;) [2001-07-27 13:01:35] [EMAIL PROTECTED] status: open [2001-07-25 11:40:51] [EMAIL PROTECTED] 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. [2001-07-25 02:10:02] [EMAIL PROTECTED] 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.) [2001-07-24 15:40:01] [EMAIL PROTECTED] 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 commentBR); // This line should be a comment print(This is the next line past the commentBR); ? /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 The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/?id=12323 Edit this bug report at http://bugs.php.net/?id=12323edit=1 -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] Bug #12323 Updated: // comment tag does not work
ID: 12323
Updated by: sniper
Reported By: [EMAIL PROTECTED]
Old Status: Feedback
Status: Open
Bug Type: Output Control
Operating System: Mac OS X
PHP Version: 4.0.6
New Comment:
status: open
Previous Comments:
[2001-07-25 11:40:51] [EMAIL PROTECTED]
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.
[2001-07-25 02:10:02] [EMAIL PROTECTED]
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.)
[2001-07-24 15:40:01] [EMAIL PROTECTED]
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
commentBR);
// This line should be a comment
print(This is the next line past the commentBR);
?
/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
[2001-07-24 14:28:59] [EMAIL PROTECTED]
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
[2001-07-24 14:27:13] [EMAIL PROTECTED]
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.
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/?id=12323
Edit this bug report at http://bugs.php.net/?id=12323edit=1
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] Bug #12323 Updated: // comment tag does not work
ID: 12323
User updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Feedback
Bug Type: Output Control
Operating System: Mac OS X
PHP Version: 4.0.6
New Comment:
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.
Previous Comments:
[2001-07-25 02:10:02] [EMAIL PROTECTED]
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.)
[2001-07-24 15:40:01] [EMAIL PROTECTED]
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
commentBR);
// This line should be a comment
print(This is the next line past the commentBR);
?
/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
[2001-07-24 14:28:59] [EMAIL PROTECTED]
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
[2001-07-24 14:27:13] [EMAIL PROTECTED]
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.
[2001-07-24 14:16:26] [EMAIL PROTECTED]
unable to reproduce on RH Linux 7.
This sounds very bogus.
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/?id=12323
Edit this bug report at http://bugs.php.net/?id=12323edit=1
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] Bug #12323 Updated: // comment tag does not work
ID: 12323 User updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Open Bug Type: Output Control Operating System: Mac OS X PHP Version: 4.0.6 New Comment: 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. Previous Comments: [2001-07-24 14:16:26] [EMAIL PROTECTED] unable to reproduce on RH Linux 7. This sounds very bogus. [2001-07-23 18:35:15] [EMAIL PROTECTED] 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 [2001-07-23 18:31:24] [EMAIL PROTECTED] 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 [2001-07-23 17:19:38] [EMAIL PROTECTED] When I use the // as the comment, the text behind the tag is displayed out to the user. I can replace it with a /* and put a */ at the end to make it work. But I was hoping I had missed some compile option or something that is causing this to not work. To make the installs on my G3 PowerMac Laptop, I have used the instructions found at: http://www.devshed.com/ Server_Side/Administration/BuildingOnOSX/ Any suggestions are welcome. Thanks, Lael Edit this bug report at http://bugs.php.net/?id=12323edit=1 -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Bug #12323 Updated: // comment tag does not work
MacOS? Hmmm... I bet the problem is in that the end-lines are not
recognized correctly. That is, the newline on a MAC ('\r') on the line
that has a comment on it is not recognized as a valid newline, thus the
closing tag ? will appear on the same line after the comment, as far
as PHP is concerned and will be commented out.
We had similar problems discussed on the list recently. Should we
ask Lael to try and fix the endline so it is either '\n' or '\r\n'? And, if
this fixes the problem look into the code and see why it does not like
the MacOS-style newlines in comments?
Just a thought
Vlad
[EMAIL PROTECTED] wrote:
ID: 12323
User updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Open
Bug Type: Output Control
Operating System: Mac OS X
PHP Version: 4.0.6
New Comment:
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
Previous Comments:
[2001-07-24 14:27:13] [EMAIL PROTECTED]
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.
[2001-07-24 14:16:26] [EMAIL PROTECTED]
unable to reproduce on RH Linux 7.
This sounds very bogus.
[2001-07-23 18:35:15] [EMAIL PROTECTED]
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
[2001-07-23 18:31:24] [EMAIL PROTECTED]
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
[2001-07-23 17:19:38] [EMAIL PROTECTED]
When I use the // as the comment, the text behind the tag
is displayed out to the user. I can replace it with a /*
and put a */ at the end to make it work. But I was
hoping I had missed some compile option or something that
is causing this to not work.
To make the installs on my G3 PowerMac Laptop, I have used
the instructions found at: http://www.devshed.com/
Server_Side/Administration/BuildingOnOSX/
Any suggestions are welcome.
Thanks,
Lael
Edit this bug report at http://bugs.php.net/?id=12323edit=1
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] Bug #12323 Updated: // comment tag does not work
ID: 12323
User updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Open
Bug Type: Output Control
Operating System: Mac OS X
PHP Version: 4.0.6
New Comment:
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
commentBR);
// This line should be a comment
print(This is the next line past the commentBR);
?
/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
Previous Comments:
[2001-07-24 14:28:59] [EMAIL PROTECTED]
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
[2001-07-24 14:27:13] [EMAIL PROTECTED]
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.
[2001-07-24 14:16:26] [EMAIL PROTECTED]
unable to reproduce on RH Linux 7.
This sounds very bogus.
[2001-07-23 18:35:15] [EMAIL PROTECTED]
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
[2001-07-23 18:31:24] [EMAIL PROTECTED]
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
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/?id=12323
Edit this bug report at http://bugs.php.net/?id=12323edit=1
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] Bug #12323 Updated: // comment tag does not work
ID: 12323
Updated by: cynic
Reported By: [EMAIL PROTECTED]
Old Status: Open
Status: Feedback
Bug Type: Output Control
Operating System: Mac OS X
PHP Version: 4.0.6
New Comment:
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.)
Previous Comments:
[2001-07-24 15:40:01] [EMAIL PROTECTED]
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
commentBR);
// This line should be a comment
print(This is the next line past the commentBR);
?
/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
[2001-07-24 14:28:59] [EMAIL PROTECTED]
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
[2001-07-24 14:27:13] [EMAIL PROTECTED]
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.
[2001-07-24 14:16:26] [EMAIL PROTECTED]
unable to reproduce on RH Linux 7.
This sounds very bogus.
[2001-07-23 18:35:15] [EMAIL PROTECTED]
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
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/?id=12323
Edit this bug report at http://bugs.php.net/?id=12323edit=1
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] Bug #12323 Updated: // comment tag does not work
ID: 12323 Updated by: cnewbill Reported By: [EMAIL PROTECTED] Status: Open Bug Type: Output Control Operating System: Mac OS X PHP Version: 4.0.6 New Comment: 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 Previous Comments: [2001-07-23 17:19:38] [EMAIL PROTECTED] When I use the // as the comment, the text behind the tag is displayed out to the user. I can replace it with a /* and put a */ at the end to make it work. But I was hoping I had missed some compile option or something that is causing this to not work. To make the installs on my G3 PowerMac Laptop, I have used the instructions found at: http://www.devshed.com/ Server_Side/Administration/BuildingOnOSX/ Any suggestions are welcome. Thanks, Lael Edit this bug report at http://bugs.php.net/?id=12323edit=1 -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] Bug #12323 Updated: // comment tag does not work
ID: 12323 Updated by: cnewbill Reported By: [EMAIL PROTECTED] Status: Open Bug Type: Output Control Operating System: Mac OS X PHP Version: 4.0.6 New Comment: 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 Previous Comments: [2001-07-23 18:31:24] [EMAIL PROTECTED] 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 [2001-07-23 17:19:38] [EMAIL PROTECTED] When I use the // as the comment, the text behind the tag is displayed out to the user. I can replace it with a /* and put a */ at the end to make it work. But I was hoping I had missed some compile option or something that is causing this to not work. To make the installs on my G3 PowerMac Laptop, I have used the instructions found at: http://www.devshed.com/ Server_Side/Administration/BuildingOnOSX/ Any suggestions are welcome. Thanks, Lael Edit this bug report at http://bugs.php.net/?id=12323edit=1 -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
