Re: Bug #12323 Updated: // comment tag does not work
| From: | Vlad Krupin | Date: | Tue, 24 Jul 2001 19:00:38 +0000 |
| Subject: | Re: Bug #12323 Updated: // comment tag does not work | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-60892@lists.php.net to get a copy of this message | ||
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
lael@evolutionmc.com wrote:
ID: 12323 User updated by: lael@evolutionmc.com Reported By: lael@evolutionmc.com 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] lael@evolutionmc.com 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] andy@php.net unable to reproduce on RH Linux 7. This sounds very bogus. ------------------------------------------------------------------------ [2001-07-23 18:35:15] cnewbill@php.net 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] cnewbill@php.net 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] lael@evolutionmc.com 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=12323&edit=1