Difference between revisions of "Koneki/LDT/Technical Discussions/Documentation Language"

From Eclipsepedia

Jump to: navigation, search
Line 53: Line 53:
  
  
This section will be processed as '''module documentation block''', when the keyword <code>@module</code> is found.
+
This section will be processed as '''module documentation block''', when the <code>@module</code> tag is found.
 
Several <code>@return</code> clauses are allowed. They are composed of a list of several type references.
 
Several <code>@return</code> clauses are allowed. They are composed of a list of several type references.
 
Those references represent types returned by this file.
 
Those references represent types returned by this file.
Line 71: Line 71:
 
  -- @field fieldnottypedname description
 
  -- @field fieldnottypedname description
 
   
 
   
Will be processed as a '''type comment block''', when the keyword <code>@type</code> is found.
+
Will be processed as a '''type comment block''', when the <code>@type</code> tag is found.
Several <code>@field</code> clauses are allowed. They consist of the keyword <code>@field</code> followed by an optional type reference as described in the file comment section, then the field name and its textual description.
+
Several <code>@field</code> clauses are allowed. They consist of the <code>@field</code> tag, followed by an optional type reference as described in the file comment section, then the field name and its textual description.
 
Textual description is '''everything''' until next line starting with <code>@</code>.
 
Textual description is '''everything''' until next line starting with <code>@</code>.
  
Line 84: Line 84:
 
  -- @return #typeref,#typeref description
 
  -- @return #typeref,#typeref description
  
Will be processed as a function comment block, when the keyword <code>@function</code> is found.
+
Will be processed as a function comment block, when the <code>@function</code> tag is found.
This keyword is followed by a scope indicator:
+
This tag is followed by a scope indicator:
 
* '''[parent = #global]''': to specify that this function will be stored in global environment.
 
* '''[parent = #global]''': to specify that this function will be stored in global environment.
 
* '''[parent = #internalrecordtyperef]''': where <code>#internalrecordtyperef</code> is a reference to a record type defined in current file. It allows to link this function to referenced record type.
 
* '''[parent = #internalrecordtyperef]''': where <code>#internalrecordtyperef</code> is a reference to a record type defined in current file. It allows to link this function to referenced record type.
Line 97: Line 97:
 
  -- @field[parent=#global] #typeref fieldname
 
  -- @field[parent=#global] #typeref fieldname
 
   
 
   
Will be processed as a field comment block, when the keyword <code>@field</code> is found.
+
Will be processed as a field comment block, when the <code>@field</code> tag is found.
This keyword is followed by a scope indicator:
+
This tag is followed by a scope indicator:
 
* '''[parent = #global]''': to specify that this field will be stored in global environment.
 
* '''[parent = #global]''': to specify that this field will be stored in global environment.
 
* '''[parent = #internalrecordtyperef]''': where <code>#internalrecordtyperef</code> is a reference to a record type defined in current file. It allows to link this field to the referenced record type.
 
* '''[parent = #internalrecordtyperef]''': where <code>#internalrecordtyperef</code> is a reference to a record type defined in current file. It allows to link this field to the referenced record type.

Revision as of 07:27, 10 February 2012

Contents

Documentation Language

Sample

------------------------------------------------------------------------------
-- short description.
-- long description
-- @module modulename
-- @return #primitivetyperef, my.module#externaltyperef, #internaltyperef description

-----------------------------------------------------------------------------
-- short description.
-- long descrition 
-- @type #recordtypename
-- @field #typeref fieldtypedname description
-- @field fieldnottypedname description

-----------------------------------------------------------------------------
-- short description.
-- long description
-- @function [parent=#global] functionname
-- @param #typref typedparamname description
-- @param untypedparamname description
-- @return #typeref, #typeref description

------------------------------------------------------------------------------
-- short description.
-- long descrition
-- @function [parent=#recordtyperef]
-- @param #typeref paramtypedname description
-- @param paramnottypedname description
-- @return #typeref,#typeref decription
------------------------------------------------------------------------------
-- short description.
-- long descrition
-- @field[parent=#global] #typref fieldname
------------------------------------------------------------------------------
-- short description.
-- long descrition
-- @field[parent=#recordtyperef] #typref fieldname

Sample detailed explanation

File comment block

------------------------------------------------------------------------------
-- short description.
-- long description
-- @module modulename 
-- @return #primitivetyperef, my.module#externaltyperef, #internaltyperef description


This section will be processed as module documentation block, when the @module tag is found. Several @return clauses are allowed. They are composed of a list of several type references. Those references represent types returned by this file. There are three kinds of type references:

  • primitive: reference to a built-in type such as string, table, boolean, ... In our syntax: #string, #table, #boolean, ...
  • internal: reference to types defined in the current file. Such as: #internaltyperef in previous sample.
  • external: reference to types defined in other modules. Such as: my.module#externaltyperef.

Textual description is everything until the next line starting with @. If no return is defined, the module will return a record internal type named #modulename.

Record comment block

------------------------------------------------------------------------------
-- short description.
-- long descrition 
-- @type #recordtypename
-- @field #typeref fieldtypedname description
-- @field fieldnottypedname description

Will be processed as a type comment block, when the @type tag is found. Several @field clauses are allowed. They consist of the @field tag, followed by an optional type reference as described in the file comment section, then the field name and its textual description. Textual description is everything until next line starting with @.

Function comment block

------------------------------------------------------------------------------
-- short description.
-- long description
-- @function [parent=#global] functionname
-- @param #typref typedparamname description
-- @param untypedparamname description
-- @return #typeref,#typeref description

Will be processed as a function comment block, when the @function tag is found. This tag is followed by a scope indicator:

  • [parent = #global]: to specify that this function will be stored in global environment.
  • [parent = #internalrecordtyperef]: where #internalrecordtyperef is a reference to a record type defined in current file. It allows to link this function to referenced record type.

Several @param clauses are allowed. They consist of @param followed by an optional type, a parameter name and a textual description, which is everything until the next line starting with a @. Several @return clauses are allowed. They consist of @return followed by a list of type references separated by comas, and a textual description as previously described.

Field comment block

------------------------------------------------------------------------------
-- short description.
-- long description
-- @field[parent=#global] #typeref fieldname

Will be processed as a field comment block, when the @field tag is found. This tag is followed by a scope indicator:

  • [parent = #global]: to specify that this field will be stored in global environment.
  • [parent = #internalrecordtyperef]: where #internalrecordtyperef is a reference to a record type defined in current file. It allows to link this field to the referenced record type.