I recommend using github markdown in the repository for documentation. Make a top level readme.md file and/or docs directory with documentation. This makes it easy for others to submit pull requests to update improve documentation too.
On Mon, Jan 4, 2016, 16:26 David Matthews <david.matth...@prolingua.co.uk> wrote: > Rob, > > On 04/01/2016 19:44, Rob Arthan wrote: > > > >> On 3 Jan 2016, at 18:33, James Clarke <jrt...@jrtc27.com> wrote: > >> > >> Hi Rob, install_pp has been deprecated for a while[1], with > >> addPrettyPrinter[2] being its replacement. Is there a reason you > >> can't use that? > >> > > Thanks for the reminder. (I’m glad to see the documentation doesn’t > > actually say “deprecated”, a word that I deprecate as a substitute > > for “not recommended” :-).) I was actually testing on an oldish > > release of ProofPower. Later releases use addPrettyPrinter. > > I avoid the use of "deprecated" in that sense although I think it's fair > to say it has now acquired a technical meaning and there's no other > exact synonym. "Not recommended" doesn't quite capture it. > > > Note that the the PolyMLStructure documentation will be out-of-date > > for version 5.6. > > The Poly/ML documentation was seriously out-of-date or simply > non-existent and during the summer I went through and brought it more > into line with the version at that stage. It will need some further work. > > David > _______________________________________________ > polyml mailing list > polyml@inf.ed.ac.uk > http://lists.inf.ed.ac.uk/mailman/listinfo/polyml
_______________________________________________ polyml mailing list polyml@inf.ed.ac.uk http://lists.inf.ed.ac.uk/mailman/listinfo/polyml
