Initially, the PlDoc wiki language was based on
is a wiki syntax that is widely accepted and not tied to a single
system. In PlDoc 2, we have adopted markdown, including many of the
limitations and extensions introduced by
Limitations are needed to avoid ambiguities due to the common use of
symbol charaters in programming languages. Extensions are desirable to
make use of already existing conventions and to support requirements of
Some of the changes in PlDoc 2 are to achieve compatibility with
project. The library documentation conventions of this project will be
based on PlDoc and the Ciao lpdoc standards. It is likely that there
will be more changes to the PlDoc format to synchronise with Commons. We
do not anticipate significant impact on existing documentation.
- Covington et
- Michael A. Covington, Roberto Bagnara, Richard A. O'Keefe, Jan
Wielemaker, Simon Price, and Simon Price. Coding guidelines for prolog
coding guidelines for prolog. pages 889--927, 2012.
- Manuel V. Hermenegildo. A documentation generator for (c)lp
systems. In John W. Lloyd, Verónica Dahl, Ulrich Furbach,
Manfred Kerber, Kung-Kiu Lau, Catuscia Palamidessi, Lu&\iacute;s Moniz
Pereira, Yehoshua Sagiv, and Peter J. Stuckey, editors, Computational
Logic, volume 1861 of Lecture Notes in Computer Science,
pages 1345--1361. Springer, 2000.
- Jeffery et
- David Jeffery, Fergus Henderson, and Zoltan Somogyi. Type classes in
mercury. In ACSC, pages 128--135. IEEE Computer Society, 2000.
- Moura, 2003
- Paulo Moura.
Logtalk - Design of an Object-Oriented Logic Programming Language.
PhD thesis, Department of Informatics, University of Beira Interior,
Portugal, September 2003.
- Mycroft &
- Alan Mycroft and Richard A. O'Keefe. A polymorphic type system for
Artif. Intell., 23(3):295--307, 1984.
- 10.1 10.3
- 10.1 10.3.3