Undocumented C functions

Michael Hind mike.hind at gmail.com
Sat Jun 5 21:02:46 UTC 2010


I am quite happy to review any documentation you add.

I have gradually reduced the number of failing tests here, over the course
of the last few months.  Initially a lot of the tests had no documentation
at all and I inserted boilerplate headers where they were missing that need
to be filled in (the documentation that is).  I, and others, have filled in
quite a bit along the way, reducing the number of failing tests here by
quite a bit.  I introduced some related documentation in the trac wiki - See
CFunctionDocs under the Tasklists And Projects on the front page.

Two things to note:

1) any added documentation needs to conform to pod line length which is, I
think 78 columns, rather than 100, and

2) once the documentation has been added and it passes the test, you need to
remove it from the TOTO list in the actual test itself.


Michael (mikehh)

Michael H. Hind

Cell: +44 (0) 7877 224 745Tel:  +44 (0) 1224 645 112
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.parrot.org/pipermail/parrot-dev/attachments/20100605/1f5b1fa2/attachment.html>

More information about the parrot-dev mailing list