# or // as comment

[delpino]

http://pear.sourceforge.net/en/standards.comments.php

C style comments (/* */) and standard C++ comments (//) are both fine. Use of Perl/shell style comments (#) is discouraged.

Anybody knows why it is discouraged? I prefer # to // because its shorter, I don't see anything wrong with it

[chrisranjana]

maybe php wants to be as far as possible different from perl.

[Mincer]

I wouldn't worry about it too much, do what you feel like unless you're coding for PEAR. Personally I always use /* */ comments in my code, that way you could have the line breaks in you file messed up, but the code will still work.

Anyway, all the standards in the world wouldn't help PEAR, what they need is better code.

[freakysid]

###################################################
# I have my own kooky little standard for using
# comments in my code.
#
# I use the # for internal documentation including:
# - A header at the top of each script with details
#   like author, date, log of changes.
# - A header to each function defined in the script
# - And sub-headings in my code to break up and explain 
#   logic.
###################################################

I then use the C style comments to temporarily comment
out code for debugging purposes

//like this
// ...


/* and
   like
   this
*/

[someonewhois]

I used to do that, but changed

Now I use:

/********** Script Name ************
 * Crap goes here
 * 
 * More
 *
 * more! :p
 * blah
 *************
 * Divded part
 *************
 *
 * The end
 ************************************/

echo "SEe?"
// $var = "TEST";
echo $var;
echo "Didn't like $var's definiton ;) "; 

[firepages]

hmmmm whatever style I use the comments always appear total gibberish only a few days later....

...with PERL of course is that the code is gibberish as well