Documentation

From Rosetta Code

Icon and Unicon

Icon

There are no formal conventions for documentation built into the Icon/Unicon. However, there are conventions for the different libraries that are supported by automation. <lang Icon>############################################################################

  1. File: filename.icn
  2. Subject: Short Description
  3. Author: Author's name
  4. Date: Date
  5. This file is in the public domain. (or other license)
  6. Long form docmentation
  7. Links:

procedure x1() #: short description of procedure </lang>

Unicon

<lang Unicon>XYZ</lang>

This example is in need of improvement:

Needs corresponding Unilib formats


[ipldoc.icn Program to collect library documentation. [iplindex.icn] Program to produce indexed listing of the program library.

TBD

J

Use scripdoc: <lang j>NB. ========================================================= NB.*apply v apply verb x to y apply=: 128!:2

NB. ========================================================= NB.*def c : (explicit definition) def=: :

NB.*define a : 0 (explicit definition script form) define=: : 0

NB.*do v name for ". do=: ".

NB.*drop v name for }. drop=: }.</lang>