Log of autodoc.git/traditional_manual/chapter

2016-11-14

2016-11-14 07:59:26 by Pontus Östlund <ponost@roxen.com>

e75d95256bd5c20c5726feca1306fbd4773be401 (291 lines) (+146/-145) ^{[

Show
| Annotate

]}
Branch: 8.0
Tags: v8.0.364, v8.0.360, v8.0.362 and v8.0.366

Major redesign of the refdoc. Also removed some obsolete stuff.

4: <dt><a name='1'></a> <h2 class='header'>21.1. Syntax</h2></dt> <dd></dd><dt><h3 class='header'>21.1.1. Line orientation</h3></dt><dd>The markup is line oriented. If you need to write a line which is very - long, it can be broken into several lines. A trailing @ on the line - indicates that it continues on the next line. The @ and the newline + long, it can be broken into several lines. A trailing <tt>@</tt> on the line + indicates that it continues on the next line. The <tt>@</tt> and the newline character will be discarded, and the lines merged. Thus:<pre> //! @variable thisVariableNameIsSoLong@ //!YouJustCantBelieveIt
28: - I love you, said Danny. - You have no right to come here after what you did to my little dog, screamed Penny in despair. - </pre></dd><dt><h3 class='header'>21.1.2. Keywords</h3></dt><dd>Keywords always begin with an at-sign: @. A @ is quoted by writing two - of them: @@. There are four types of keywords (the keywords in []'s + </pre></dd><dt><h3 class='header'>21.1.2. Keywords</h3></dt><dd>Keywords always begin with an at-sign: <tt>@</tt>. A <tt>@</tt> is quoted by writing two + of them: <tt>@@</tt>. There are four types of keywords (the keywords in []'s are examples of keywords of the different types):<ol> - <li> Meta keywords [@decl, @class, @endclass, @module and @endmodule] + <li> Meta keywords <tt>[@decl, @class, @endclass, @module and @endmodule]</tt> Must stand alone on one line, preceded only by whitespace. These are not really part of the markup. They must come before any text or other keywords in the doc block. They provide information about what
39: documentation. Meta keywords have keyword specific parameter syntaxes.</li> - <li> Delimiter keywords [@param, @member, @item, @note, ...] + <li> Delimiter keywords <tt>[@param, @member, @item, @note, ...]</tt> Must stand alone on one line, preceded only by whitespace. These are keywords that begin a section inside their block. They have no end marker, but rather the section ends when the next delimiter keyword on the same level is found. Can have parameters.</li> - <li> Block/endblock keywords [@dl - @enddl, @mapping - @endmapping, ...] + <li> Block/endblock keywords <tt>[@dl - @enddl, @mapping - @endmapping, ...]</tt> Must stand alone on one line, preceded only by whitespace. These open or close a block. If a block is started with @foo, it must end with a matching @endfoo. The lines inside the block can be divided into sections by using delimiter keywords. The start keyword can have parameters, but the corresponding end keyword can not.</li> - <li> Short markup keywords [@ref{..@}, @i{..@}, ...] + <li> Short markup keywords <tt>[@ref{..@}, @i{..@}, ...]</tt> These are used in the text to perform cosmetic tasks, for example - changing text to italic (@i), teletype(@tt) or marking a word as a - reference to a pike entity (@ref). They can be nested, but a short + changing text to italic (<tt>@i</tt>), teletype(<tt>@tt</tt>) or marking a word as a + reference to a pike entity (<tt>@ref</tt>). They can be nested, but a short markup keyword can not contain a keyword of types 1-3. They begin - with @keyword{ and end with @}.</li> + with <tt>@keyword{ and end with @}</tt>.</li> - <li> The magic keyword @xml{ ... @} + <li> The magic keyword <tt>@xml{ ... @}</tt> This is a special keyword that provides an escape to XML. All ordinary text inside it is passed unquoted to the output. However, the short markup keywords are still valid and may be used inside it, and thus - @ must still be quoted with @@. < and > must also be quoted unless + <tt>@</tt> must still be quoted with <tt>@@</tt>. <tt><</tt> and <tt>></tt> must also be quoted unless the intention really is to write XML. For example: <example>
86: //! @param y //! The coordinates of the vector. </pre> - Above, the two @param's x and y are grouped together and share the + Above, the two <tt>@param</tt>'s x and y are grouped together and share the same docstring: "The coordinates of the vector.". It is an error to try to group together different keywords:<pre> //! Error, can't group @note and @param:
94: //! @note //! Don't use this function. At all. Ever. </pre> - </dd><dt><h3 class='header'>21.1.4. Keyword parameters</h3></dt><dd>After the leading @keyword (that may be preceded only by whitespace) + </dd><dt><h3 class='header'>21.1.4. Keyword parameters</h3></dt><dd>After the leading <tt>@keyword</tt> (that may be preceded only by whitespace) on the line, the rest of the line is interpreted as a parameter list. The syntax of this parameter list can be different depending on the keyword:<ol>
129: //! @wrong "Aww, come on now, this worked fine in C64 basic! </example> - If a quoted parameter is too long to fit in one line, use the @ at + If a quoted parameter is too long to fit in one line, use the <tt>@</tt> at the end of the line to merge it with the following: <example>
148: The parameter will be a string with two characters, a backslash followed by the letter n.</li> </ol></dd><dt><h3 class='header'>21.1.5. Grammar</h3></dt><dd>Here comes a BNF-ish grammar for documentation blocks. Note that - before the parsing of the block, all lines ending with a @ will be + before the parsing of the block, all lines ending with a <tt>@</tt> will be merged with the next line (see (a) above)<pre> docblock: metaline*, blockbody
230: *! yadda yadda yadda */ </pre> - Note that only lines that start with *! count, so above are only two - doc lines. Any whitespace before the leading *! is skipped, so that + Note that only lines that start with <tt>*!</tt> count, so above are only two + doc lines. Any whitespace before the leading <tt>*!</tt> is skipped, so that the lines can be indented freely.In the C files, no parsing of the surrounding code is done. The context lies completely in the doc comments themselves, and the target of the doc comment is determined by special meta keywords that are not
262: /*! @endmodule */ </pre> - The @module and @class too keywords are to work like segment - directives in assembler source files. That is, you can have "@module - foo" in several C files, if the module source is spread over multiple + The <tt>@module</tt> and <tt>@class</tt> too keywords are to work like segment + directives in assembler source files. That is, you can have <tt>@module + foo</tt> in several C files, if the module source is spread over multiple files. However, if you write doc for the module itself in several places, an error will be triggered.</dd><dt><h3 class='header'>21.2.2. Pike files</h3></dt><dd>Doc comments look like:<pre> //! yadda yadda yadda //! yadda yadda </pre> To be considered one doc block, the comments must be separated only by - whitespace and _one_ "\n", that is they have to be on adjacent lines + whitespace and <tt>\n</tt>, that is they have to be on adjacent lines in the code. Each doc block in the Pike code has one or more targets; the Pike entities (modules, classes, variables etc.) that the doc block is documenting. The target of a doc comment is the coherent
317: int very_short() { return 4711; } int even_shorter() { return 0; } </pre> - In Pike files, you can not use @class or @module to tell which module + In Pike files, you can not use <tt>@class</tt> or <tt>@module</tt> to tell which module or class you are in. To document a class, you simply write:<pre> //! Doc for the class class CheeseMaker
334: void create(string s) { ... } } </pre> - The parser will automatically identify a() as a member method of the - class CheeseMaker, and will detect that Earth is inherited by - CheeseMaker. If a class has no documentation comment, it's internals + The parser will automatically identify <tt>a()</tt> as a member method of the + class <tt>CheeseMaker</tt>, and will detect that <tt>Earth</tt> is inherited by + <tt>CheeseMaker</tt>. If a class has no documentation comment, it's internals will not be examined, thus it is an error if a class contains documentation comments but is itself undocumented:<pre> class a()
347: </pre> A special inlining case is that of functions and classes. When documenting these, the doc comment can be put between the head of the function/class, - and the opening "{", like this:<pre> + and the opening <tt>{</tt>, like this:<pre> class Roy //! Documentation for Roy {
364: If a doc block is the first in a file, and it has no target, then it is treated as doc for the file (or rather: the module/class that the file compiles into) itself. In any other case it is an error to have a - targetless doc block. A target can also be set with the @decl meta - keyword. If a doc comment begins with some @decl keywords, these - @decl's act just like real declarations standing next to the doc. + targetless doc block. A target can also be set with the <tt>@decl</tt> meta + keyword. If a doc comment begins with some <tt>@decl</tt> keywords, these + <tt>@decl</tt>'s act just like real declarations standing next to the doc. Thus:<pre> //! @decl int a(int x) //! @decl int b(int x)
383: ..... } </pre> - In _one_ case it is legal to have both an adjacent declaration and - the @decl keyword at the block beginning. That is when you document + In case it is legal to have both an adjacent declaration and + the <tt>@decl</tt> keyword at the block beginning. That is when you document "polymorph" methods. Then the adjacent declaration must be a method, - and all @decl's must be methods that have the same name as the real + and all <tt>@decl</tt>'s must be methods that have the same name as the real method:<pre> //! @decl float cube(float x) //! @decl int cube(int x)
398: .... } </pre> - The real method prototype is discarded in favour to the @decl'ed - variants, who will be shown in the documentation instead.One problem that is unsolved so far is how to handle #if .. #else .. - #endif constructions. The approach so far has been to ignore + The real method prototype is discarded in favour to the <tt>@decl</tt>'ed + variants, who will be shown in the documentation instead.One problem that is unsolved so far is how to handle <tt>#if .. #else .. + #endif</tt> constructions. The approach so far has been to ignore preprocessor directives totally. For example, the parser does not handle:<pre> #ifdef MALE
414: </pre> It a portion of the code is unextractable because it contains too much preprocessor macros and stuff, you can make the extractor skip it by using - @ignore:<pre> + <tt>@ignore</tt>:<pre> //! @ignore HERE_ARE_SOME_STRANGE_THINGS
424: //! @endignore </pre> - All @ignore-@endignore sections of the file are removed before any extraction - is done, so they can cross class boundaries and the like. You can nest @ignore - inside eachother. Another application for @ignore is to hide actual class + All <tt>@ignore-@endignore</tt> sections of the file are removed before any extraction + is done, so they can cross class boundaries and the like. You can nest <tt>@ignore</tt> + inside eachother. Another application for <tt>@ignore</tt> is to hide actual class boundaries from the extractor:<pre> //! @ignore class C {
444: <h2 class='header'>21.3. Pike autodoc tags</h2></dt> <dd>We have defined some different categories of markup, each with its own semantics. Seen from the parser, there are two main construct levels:<ul> - <li> The "what-are-we-documenting level" constructs; @decl for Pike files - and @module, @endmodule, @class and @endclass on top of that for C - files. These are the meta level tags covered in section a).</li> + <li> The "what-are-we-documenting level" constructs; <tt>@decl</tt> for Pike files + and <tt>@module</tt>, <tt>@endmodule</tt>, <tt>@class</tt> and <tt>@endclass</tt> + on top of that for C files. These are the meta level tags covered in section a).</li> <li> Inside-of-comment level constructs for documentation markup, covered in sections b), c) and d).</li> </ul>All markup can also be divided into categories based on their look and semantics; there are three categories here (with examples):<ul> <li> Grouping constructs that mark the opening/closing of a section of - some sort (@mapping/@endmapping, @dl/@enddl, @module/@endmodule). + some sort (<tt>@mapping/@endmapping, @dl/@enddl, @module/@endmodule</tt>). Most of these not already covered by secion a) appear in b).</li> <li> subdividers that break up an outer grouping construct into - subsections (@member, @item, @param)</li> + subsections (<tt>@member, @item, @param</tt>)</li> <li> short text markup constructs that basically map to XML containers - (@i{...@}, @ref{...@})</li> + (<tt>@i{...@}, @ref{...@}</tt>)</li> </ul></dd><dt><h3 class='header'>21.3.1. Meta level tags</h3></dt><dd>These tags all serve the purpose of denoting what pike entities your comments should be tied to. This is particularly needed in (and in part only applies to) C files, where the autodoc extractor does not
468: Keyword: @module Legal for: C files only (neither needed nor legal for Pike files) Arguments: (the last segment of) the module name (ie no "." allowed) - </pre>Example: To document the module Parser.XML module, you need two + </pre>Example: To document the module <tt>Parser.XML</tt> module, you need two consecutive module tags:<pre> /*! @module Parser */ /*! @module XML */ </pre> - A @module keyword sets the scope of documentation comments following - it. @module tags nest, as shown in the example above, and must be + A <tt>@module</tt> keyword sets the scope of documentation comments following + it. <tt>@module</tt> tags nest, as shown in the example above, and must be ended with a matching number of @endmodule tags, as in:<pre> /*! @endmodule XML */ /*! @endmodule Parser */ </pre> - A @module keyword may also have a text child documenting the module + A <tt>@module</tt> keyword may also have a text child documenting the module itself:<pre> /*! @module Parser *!
487: *! @[Parser.XML], @[Parser.Pike] and @[Parser.C] are housed. */ </pre> - There are two special @module targets available; the "predef::" module - and the "lfun::" module. The predef:: module, although more of a scope + There are two special @module targets available; the <tt>predef::</tt> module + and the <tt>lfun::</tt> module. The <tt>predef::</tt> module, although more of a scope than a module, contains the definitions for all methods in Pike's - predef:: scope, as in:<pre> + <tt>predef::</tt> scope, as in:<pre> /*! @module predef:: *! @decl int equal(mixed a, mixed b) *! This function checks if the values @[a] and @[b] are equal. *! @endmodule */ </pre> - The "lfun::" module scope does not legally exist in Pike, but it + The <tt>lfun::</tt> module scope does not legally exist in Pike, but it houses the docs for all lfuns (the virtual methods for fulfilling the Pike object API). An example:<pre> /*! @module lfun::
506: *! @endmodule */ </pre> - This also means that referencing (via @ref{...@} or @[...]) the lfun - documentation strings can be done using @[lfun::`!=] and the like, as - can predefs via @[predef::sort()] et cetera.<pre> + This also means that referencing (via <tt>@ref{...@}</tt> or <tt>@[...]</tt>) the lfun + documentation strings can be done using <tt>@[lfun::`!=]</tt> and the like, as + can predefs via <tt>@[predef::sort()]</tt> et cetera.<pre> Keyword: @endmodule Legal for: C files only (neither needed nor legal for Pike files) Arguments: (the last segment of) the module name (optional) - </pre>>When the optional argument to @endmodule is given (for code clarity), + </pre>>When the optional argument to <tt>@endmodule</tt> is given (for code clarity), the extractor will verify that the module scope you close was indeed - the one you opened, as in the @module example above. The following + the one you opened, as in the <tt>@module</tt> example above. The following would trigger an error:<pre> /*! @module Parser *! @module XML */
532: Keyword: @class Legal for: C files only (neither needed nor legal for Pike files) Arguments: (the last segment of) the class name (ie no "." allowed) - </pre>Example: to document the Process.create_process class, you would use:<pre> + </pre>Example: to document the <tt>Process.create_process</tt> class, you would use:<pre> /*! @module Process *! @class create_process */ </pre> - And end the scope similar to @module:<pre> + And end the scope similar to <tt>@module</tt>:<pre> /*! @endclass create_process *! @endmodule Process */ </pre> - Like @module tags, @class tags may be nested any number of levels + Like <tt>@module</tt> tags, <tt>@class</tt> tags may be nested any number of levels (when documenting subclasses to subclasses to subclasses to ...).<pre> Keyword: @endclass Legal for: C files only (neither needed nor legal for Pike files) Arguments: (the last segment of) the class name (optional) - </pre>When the optional argument to @endclass is given (for code clarity), + </pre>When the optional argument to <tt>@endclass</tt> is given (for code clarity), the extractor will verify that the class scope you close was indeed - the one you opened, just as with @endmodule above.<pre> + the one you opened, just as with <tt>@endmodule</tt> above.<pre> Keyword: @decl Legal for: All source code (C and Pike files) Arguments: (the last segment of) the identifier name (ie "." illegal) - </pre>The @decl keyword is used to target a specific (...more to come! :-)<pre> + </pre>The <tt>@decl</tt> keyword is used to target a specific (...more to come! :-)<pre>

autodoc.git/ traditional_manual/ chapter_21.html

2016-11-14

2016-11-14 07:59:26 by Pontus Östlund <ponost@roxen.com>