Skip to main content
WordPress Development

Return to Answer

Commonmark migration
Source Link
Community Bot
Community Bot
  • 1

Comment using PhpDoc

##Comment using PhpDoc BestBest practice is close to the PhpDoc style. If you don't use an IDE like "Eclipse", you can just take a look at the PhpDoc Manual.

You don't have to know exactly how this works. Professional Developers can read the code anyway and just need this as a summary. Hobby coders and users might appreciate the way you explain it on the same knowledge level.

##Comment using PhpDoc Best practice is close to the PhpDoc style. If you don't use an IDE like "Eclipse", you can just take a look at the PhpDoc Manual.

You don't have to know exactly how this works. Professional Developers can read the code anyway and just need this as a summary. Hobby coders and users might appreciate the way you explain it on the same knowledge level.

Comment using PhpDoc

Best practice is close to the PhpDoc style. If you don't use an IDE like "Eclipse", you can just take a look at the PhpDoc Manual.

You don't have to know exactly how this works. Professional Developers can read the code anyway and just need this as a summary. Hobby coders and users might appreciate the way you explain it on the same knowledge level.

Changed the title from colloquial suggestion to an imperative. Edited a bit.
Source Link
MikeSchinkel
MikeSchinkel
  • 37.5k
  • 14
  • 116
  • 132

Don't be afraid of commenting

Best practice is close to the PhpDoc style. If you don't use an IDE like "eclipse", you can just take a look [at the DhpDoc Manual][1].

##Comment using PhpDoc Best practice is close to the PhpDoc style. If you don't use an IDE like "Eclipse", you can just take a look at the PhpDoc Manual.

You don't have to know exactly how this works. Professional Developers can read the code anyway and just need this as a summary. Hobby coders and users might appreciate the way you explain it on the same knowledge level. Therefore: Don't be afraid of commenting.

Don't be afraid of commenting

Best practice is close to the PhpDoc style. If you don't use an IDE like "eclipse", you can just take a look [at the DhpDoc Manual][1].

You don't have to know exactly how this works. Professional Developers can read the code anyway and just need this as a summary. Hobby coders and users might appreciate the way you explain it on the same knowledge level. Therefore: Don't be afraid of commenting.

##Comment using PhpDoc Best practice is close to the PhpDoc style. If you don't use an IDE like "Eclipse", you can just take a look at the PhpDoc Manual.

You don't have to know exactly how this works. Professional Developers can read the code anyway and just need this as a summary. Hobby coders and users might appreciate the way you explain it on the same knowledge level.

Post Made Community Wiki
Source Link
kaiser
kaiser
  • 50.8k
  • 27
  • 150
  • 244

Don't be afraid of commenting

Best practice is close to the PhpDoc style. If you don't use an IDE like "eclipse", you can just take a look [at the DhpDoc Manual][1].

You don't have to know exactly how this works. Professional Developers can read the code anyway and just need this as a summary. Hobby coders and users might appreciate the way you explain it on the same knowledge level. Therefore: Don't be afraid of commenting.