comment on

I have a good story for you. At least a funny one. I'm very multilingual in terms of programming languages. I know perl, c, some c++, java, etc...

While at a php gig, I would use perl style comments. This isn't bad. php inherited perl's/shell's commenting style as well as c's. Anyway, I had a line I wnated to comment, and used the pound/number sign: #. Things worked fine.

They pushed a release out with my new code, and everything started breaking left and right. Ugly sight. Eventually, the "CTO" of the company went out into production and looked at my code. "What is this?!" Pointing at my humble pound symbol. "It's a comment." A whole bruhaha was started about how comments are not allowed in production code and what not. First I had heard of the rule. THey traced it back to a process that would strip out comments and extra spaces, 'cause php would be "that much faster without extra characters"..

Consequentally, out of 20 or so developers, none of them ever heard of using # symbols for comments in php. :\

In reply to Re: hangover from perl... by exussum0
in thread hangover from perl... by kiat

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


There's more than one way to do things
	PerlMonks