This is down to changes that were made for new versions of ZPE.
External documentation is done using the
This means when the code is compiled, using the -h doc command on the compiled file and requesting the documentation by name will return the text that was allocated to that documentation:
@doc "MyFunction : This function returns true" function MyFunction () return true end function
The description must be quoted after the @doc directive. This is available only as of version 1.4.1. Previous versions use a different system.
This kind of documentation can be very useful if you are distributing your compiled code or planning to add it as a library.
Accessing it again is done with the -h ZAC applied on a compiled script.
zpe -h doc -f file.zex -s $function_name
In older versions of the parser, internal documentation can be exported using @ commands within multiline comments.
/*@doc My function:This function returns true*/
The semi-colon in the middle splits the documentation into two halves, one for the name (on the left) and one for the description (on the right).
When using the @ commands, the comment must use the multiline comment symbols /* and */.
S1s and S2s really enjoyed the lesson on cybercrime using the lesson on How to Rob A Bank on… https://t.co/MxjDYE2JFu
6 months ago
S2s doing really well in hardware test! Also really enjoying doing tests electronically rather than on paper.… https://t.co/ritdfcW6Mw
7 months ago
S1 and S2 pupils listing input and output devices and giving answers such as keyboard and mouse but there were also… https://t.co/dGxDkYqFxo
7 months ago