PDP Document Code Comment Specification

1. What is phpDocumentor?<br>PHPDocumentor is a tool written in PHP. For PHP programs with standard annotations, it can quickly generate API documents with cross-reference, index and other functions. The old version is phpdoc. Starting from 1.3.0, it has been renamed phpDocumentor. The new version adds support for php5 syntax. At the same time, documents can be generated by operating on the client browser, and the documents can be converted to PDF, HTML, There are several forms of CHM, which are very convenient. <br>When PHPDocumentor works, it will scan the PHP source code under the specified directory, scan the keywords, intercept the comments that need to be analyzed, then analyze the special tags in the comments, generate an xml file, and then based on the analyzed classes and modules Information, establish corresponding index, and generate xml files. For the generated xml files, use customized templates to output files in the specified format. <br>2. Install phpDocumentor<br> Like other modules under pear, the installation of phpDocumentor is also divided into two methods: automatic installation and manual installation. Both methods are very convenient: <br>a. Automatically install through pear<br>Enter <br>pear install PhpDocumentor<br>b． Manual installation<br>Download the latest version of PhpDocumentor (now 1.4.0) at http://manual.phpdoc.org/ and unzip the content. <br>3. How to use PhpDocumentor to generate documents <br>Command line method: <br>In the directory where phpDocumentor is located, enter <br>Php –h<br> and you will get a detailed parameter list. Several important parameters are as follows: <br>-f The name of the file to be analyzed, more Each file is separated by commas <br>-d The directory to be analyzed, multiple directories are separated by commas <br>-t The storage path of the generated document <br>-o The output document format, the structure is output format: converter name: template directory. <br>For example: phpdoc -o HTML:frames:earthli -f test.php -t docs<br>Web interface generation<br>In the new phpdoc, in addition to generating documents under the command line, you can also generate documents on the client browser , the specific method is to first put the content of PhpDocumentor in the apache directory so that it can be accessed through the browser. After access, the following interface will be displayed: <br>Click the files button, select the php file or folder to be processed, and you can also specify the Files to ignore under the interface to ignore the processing of certain files. <br>Then click the output button to select the storage path and format of the generated document. <br>Finally click create, and phpdocumentor will automatically start generating the document. The progress and status of the generation will be displayed at the bottom. If successful, it will display <br>Total Documentation Time: 1 seconds<br>done<br>Operation Completed!!<br>Then, we can view the generated document. If it is in pdf format, the name defaults to documentation.pdf. <br>4． Add standardized comments to PHP code<br>PHPDocument generates documents from the comments of your source code, so the process of commenting on your program is also the process of compiling documentation. <br>From this point of view, PHPdoc encourages you to develop good programming habits and try to use specifications and clear text to annotate your program. At the same time, it more or less avoids some problems of out-of-synchronization between document preparation and document updates afterwards. . <br> In phpdocumentor, comments are divided into documentation comments and non-documentation comments. <br>So-called documentation comments are multi-line comments placed in front of specific keywords. Specific keywords refer to keywords that can be analyzed by phpdoc, such as class, var, etc. For details, please refer to Appendix 1. <br>Those that are not in the key Comments that precede the word or are not standardized are called non-documentation comments. These comments will not be analyzed by phpdoc and will not appear in the API document you generate. <br>3.2 How to write documentation comments: <br> All documentation comments are a multi-line comment starting with /**, which is called DocBlock in phpDocumentor. DocBlock refers to help information about a certain keyword written by software developers. , so that others can know the specific purpose of this keyword and how to use it. PhpDocumentor stipulates that a DocBlock contains the following information: <br>1. Function brief description area <br>2. Detailed description area <br>3. Mark tag <br>The first line of the documentation comment is the function description area, and the text generally describes the class and methods concisely Or the function of the function, the text of the function brief description will be displayed in the index area in the generated document. The content of the function description area can be ended by a blank line or. <br>After the function description area is a blank line, followed by a detailed description area. This part mainly describes the function and purpose of your API in detail, and if possible, also You can give examples of usage, etc. In this section, you should focus on clarifying the general purpose and usage of your API functions or methods, and indicate whether it is cross-platform (if involved). For platform-related information, you should treat it differently from general information. , the usual approach is to start a new line, and then write Notes or special information on a specific platform. This information should be enough so that your readers can write corresponding test information, such as boundary conditions, parameters ranges, breakpoints, etc.<br>After that, there is also a blank line, and then the document tag, indicating some technical information, mainly the call parameter type, return value and type, inheritance relationship, related methods/functions, etc. <br> Regarding document marking, please refer to Section 4: Document Marking for details. <br>You can also use tags such as in document comments. Please refer to Appendix 2 for details. &lt;br&gt;The following is an example of a documentation comment&lt;br&gt;/**&lt;br&gt;* Function add, implements the addition of two numbers&lt;br&gt;*&lt;br&gt;* A simple addition calculation, the function accepts two numbers a, b, and returns their sum c&lt;br&gt;* &lt;br&gt;* @param int The addend &lt;br&gt;* @param int is Addend &lt;br&gt;* @return integer &lt;br&gt;*/&lt;br&gt;function Add($a, $b)&lt;br&gt;{&lt;br&gt; return $a+$b;&lt;br&gt;}&lt;br&gt;The generated documentation is as follows:&lt;br&gt;Add&lt;br&gt;integer Add( int $a, int $b) &lt;br&gt;[line 45]&lt;br&gt;Function add, implements the addition of two numbers&lt;br&gt;Constants A simple addition calculation, the function accepts two numbers a, b, and returns their sum c&lt;br&gt;Parameters&lt;br&gt;? int $ a - addend &lt;br&gt;? int $b - addend &lt;br&gt;5． Document tags: &lt;br&gt;The scope of use of document tags refers to the keywords or other document tags that the tag can be used to modify. &lt;br&gt;All documentation tags start with @ after * on each line. If the @ mark appears in the middle of a paragraph, the mark will be treated as normal content and ignored. &lt;br&gt;@access&lt;br&gt;Usage scope: class, function, var, define, module&lt;br&gt;This tag is used to indicate the access permission of keywords: private, public or protected&lt;br&gt;@author&lt;br&gt;Indicate the author&lt;br&gt;@copyright&lt;br&gt;Usage scope: class, function , var, define, module, use&lt;br&gt;Indicate copyright information&lt;br&gt;@deprecated&lt;br&gt;Usage scope: class, function, var, define, module, constent, global, <strong>include</strong>&lt;br&gt;Indicate unused or obsolete keywords&lt;br&gt;@example&lt;br&gt;This tag Used to parse a file content and highlight them. Phpdoc will try to read the file <strong> content from the file path given by this tag </strong> @const &lt;br&gt; Use scope: define &lt;br&gt; Used to specify the constants defined in php &lt;br&gt; @final &lt;br&gt; Use scope: class, function, var &lt;br&gt; Specify keywords It is a final class, method, and attribute, and is prohibited from being derived or modified. &lt;br&gt;@filesource&lt;br&gt;Similar to example, except that this tag will directly read the content of the currently parsed php file and display it. &lt;br&gt;@global&lt;br&gt;Indicates the &lt;br&gt;global variable referenced in this function<strong></strong>@ingore&lt;br&gt; is used to ignore the specified keyword in the document&lt;br&gt;@license&lt;br&gt;Equivalent to <a> in the html tag, first the URL, then The content to be displayed&lt;br&gt;For example </a><a href="%E2%80%9Dhttp://www.baidu.com%E2%80%9D">&lt;br&gt;Baidu<strong></strong></a>can be written as @license http://www.baidu.com &lt;br&gt;Baidu<strong></strong> @link&lt;br&gt;Similar to license&lt;br&gt;but you can also point to any keyword in the document through link&lt;br&gt;@name&lt;br&gt;Specify an alias for the keyword. &lt;br&gt;@package&lt;br&gt;Usage scope: page level -> define, function, &lt;br&gt;include<strong></strong> Class level -> class, var, methods&lt;br&gt; Used to logically group one or several keywords into a group. &lt;br&gt;@abstrcut&lt;br&gt;Indicates that the current class is an abstract class &lt;br&gt;@param&lt;br&gt;Indicates the parameters of a function &lt;br&gt;@return&lt;br&gt;Indicates the return pointer of a method or function &lt;br&gt;@static&lt;br&gt;Indicates that the keyword is static. &lt;br&gt;@var&lt;br&gt;Indicate the variable type&lt;br&gt;@version&lt;br&gt;Indicate the version information&lt;br&gt;@todo&lt;br&gt;Indicate areas that should be improved or not implemented&lt;br&gt;@throws&lt;br&gt;Indicate the error exceptions that this function may throw, and the extreme situations&lt;br&gt;As mentioned above, Ordinary document tags must be marked with @ at the beginning of each line. In addition, there is also a tag called inline tag, represented by {@}, which includes the following types: &lt;br&gt;{@link}&lt;br&gt;Usage is the same as @link &lt;br&gt;{@source}&lt;br&gt;Display the content of a function or method&lt;br&gt;6. Some comment specifications &lt;br&gt;a. Comments must be in the form &lt;br&gt;/**&lt;br&gt;* XXXXXXX&lt;br&gt;*/&lt;br&gt; &lt;br&gt;b. For functions that reference &lt;br&gt;global variables<strong>, glboal tags must be used. </strong>c. For variables, their types (int, string, bool...) must be marked with var &lt;br&gt;d. Functions must indicate their parameters and return values ​​through param and return markers &lt;br&gt;e. For variables that appear twice or more Keywords should be ignored through ingore and only one should be kept. Where other functions or classes are called, link or other tags should be used to link to the corresponding part to facilitate the reading of the document. &lt;br&gt;g. Use non-documentation comments where necessary to improve code readability. &lt;br&gt;h. Keep descriptive content concise and to the point, using phrases rather than sentences whenever possible. &lt;br&gt;i.&lt;br&gt;Global variables&lt;br&gt;, <strong>static variables</strong> and constants must be described with corresponding tags<strong>7. Summary</strong>phpDocumentor is a very powerful automatic document generation tool. It can help us write standardized comments and generate easy-to-understand structures. Clear documentation is very helpful for our code upgrades, maintenance, handover, etc.&lt;br&gt;For more detailed instructions about phpDocumentor, you can check it out on its official website&lt;br&gt;http://manual.phpdoc.org/&lt;br&gt;8. Appendix&lt;br&gt;Appendix 1:&lt;br&gt;Keywords that can be recognized by phpdoc:&lt;br&gt;<strong>include</strong>&lt;br&gt;<strong>require</strong>&lt;br&gt;<strong>include</strong>_once&lt;br&gt;<strong>require</strong>_once&lt;br&gt;define&lt;br&gt;function&lt;br&gt;global&lt;br&gt;class&lt;br&gt;Appendix 2&lt;br&gt; Tags that can be used in the document &lt;br&gt;<b> &lt;br&gt;<code> &lt;br&gt;&lt;br&gt; &lt;br&gt;<kdb>&lt;br&gt;<li> &lt;br&gt;<pre class="brush:php;toolbar:false">&lt;br&gt;</pre> <ul> &lt;br&gt;<samp>&lt;br&gt;<var>&lt;br&gt;Appendix 3: &lt;br&gt; A piece of php code with canonical comments&lt;br&gt;<?php &lt;br&gt;/**&lt;br&gt;* Sample File 2, phpDocumentor Quickstart&lt;br&gt;* &lt;br&gt;* This file demonstrates the rich information that can be <strong>include</strong>d in&lt;br&gt;* in-code documentation through DocBlocks and tags.&lt;br&gt;* @author Greg Beaver <cellog>&lt;br&gt;* @version 1.0&lt;br&gt;* @package sample&lt;br&gt;*/&lt;br&gt;// sample file #1&lt;br&gt;/**&lt;br&gt;* Dummy <strong>include</strong> value, to demonstrate the parsing power of phpDocumentor&lt;br&gt;*/&lt;br&gt;<strong>include</strong>_once 'sample3.php';&lt;br&gt;/ **&lt;br&gt;* Special global variable declaration DocBlock&lt;br&gt;* @global integer $GLOBALS['_myvar'] &lt;br&gt;* @name $_myvar&lt;br&gt;*/ &lt;br&gt;$GLOBALS['_myvar'] = 6;&lt;br&gt;/**&lt;br&gt;* Constants&lt;br&gt;*/&lt;br&gt;/**&lt;br&gt;* first constant&lt;br&gt;*/&lt;br&gt;define('testing', 6);&lt;br&gt;/** &lt;br&gt;* second constant&lt;br&gt;*/&lt;br&gt;define('anotherconstant', strlen('hello'));&lt;br&gt;/**&lt;br&gt;* A sample function docblock&lt;br&gt;* @global string document the fact that this function uses $_myvar&lt;br&gt;* @staticvar integer $staticvar this is actually what is returned&lt;br&gt;* @param string $param1 name to declare&lt;br&gt;* @param string $param2 value of the name&lt;br&gt;* @return integer &lt;br&gt;*/&lt;br&gt;function firstFunc($param1, $param2 = 'optional')&lt;br&gt;{&lt;br&gt; static $staticvar = 7;&lt;br&gt; global $_myvar;&lt;br&gt; return $staticvar;&lt;br&gt;}&lt;br&gt;/**&lt;br&gt;* The first example class, this is in the same package as the&lt;br&gt;* procedural stuff in the start of the file&lt;br&gt;* @package sample&lt;br&gt;* @subpackage classes&lt;br&gt;*/&lt;br&gt;class myclass {&lt;br&gt; /**&lt;br&gt; * A sample private variable, this can be hidden with the --parseprivate&lt;br&gt; * option&lt;br&gt; * @access private&lt;br&gt; * @var integer|string&lt;br&gt;*/&lt;br&gt; var $firstvar = 6;&lt;br&gt; /**&lt;br&gt; * @link http://www.example.com Example link&lt;br&gt; * @see myclass()&lt;br&gt; * @uses testing, anotherconstant&lt;br&gt; * @var array &lt;br&gt; */&lt;br&gt; var $secondvar =&lt;br&gt; array(&lt;br&gt; 'stuff' =>&lt;br&gt; array(&lt;br&gt; 6,&lt;br&gt; 17,&lt;br&gt; 'armadillo'&lt;br&gt; ),&lt;br&gt; testing => anotherconstant&lt;br&gt; );&lt;br&gt; /**&lt;br&gt; * Constructor sets up {@link $firstvar}&lt;br&gt;* /&lt;br&gt; function myclass()&lt;br&gt; {&lt;br&gt; $this->firstvar = 7;&lt;br&gt; }&lt;br&gt; /**&lt;br&gt; * Return a thingie based on $paramie&lt;br&gt; * @param boolean $paramie &lt;br&gt; * @return integer|babyclass&lt;br&gt;*/&lt;br&gt; function parentfunc($paramie)&lt;br&gt; {&lt;br&gt; if ($paramie) {&lt;br&gt; return 6;&lt;br&gt; } else {&lt;br&gt; return new babyclass;&lt;br&gt; }&lt;br&gt; }&lt;br&gt;}&lt;br&gt;/**&lt;br&gt;* @package sample1&lt;br&gt;*/&lt;br&gt;class babyclass extends myclass {&lt;br&gt; /**&lt;br&gt; * The answer to Life, the Universe and Everything&lt;br&gt; * @var integer &lt;br&gt;*/&lt;br&gt; var $secondvar = 42;&lt;br&gt; /**&lt;br&gt; * Configuration values&lt;br&gt; * @var array &lt;br&gt;*/&lt;br&gt; var $thirdvar;&lt;br&gt; /**&lt;br&gt; * Calls parent constructor, then increments {@link $firstvar}&lt;br&gt;*/&lt;br&gt; function babyclass()&lt;br&gt; {&lt;br&gt; parent::myclass();&lt;br&gt; $this->firstvar++;&lt;br&gt; }&lt;br&gt; /**&lt;br&gt; * This always returns a myclass&lt;br&gt; * @param ignored $paramie &lt;br&gt; * @return myclass &lt;br&gt; */&lt;br&gt; function parentfunc($paramie)&lt;br&gt; {&lt;br&gt; return new myclass;&lt;br&gt; }&lt;br&gt;}&lt;br&gt;?></cellog></var></samp> </ul> </li></kdb>

The above introduces the PDP Document code comment specifications, including require, include, global variables, precautions, and Baidu content. I hope it will be helpful to friends who are interested in PHP tutorials.