Undocumented C functions
mike.hind at gmail.com
Sun Jun 13 18:04:58 UTC 2010
compilers/pirc/src/pircapi.c does not look right to me, maybe I am wrong,
but, I don't think it conforms to correct HEADERIZER practice.
Who is our HEADERIZER guru, petdance++ I believe?
Cheers, Michael (mikehh)
On 13 June 2010 18:14, James E Keenan <jkeen at verizon.net> wrote:
> Status of efforts in cfunctionsdocs branch:
> 1. Have reduced number of files failing t/codingstd/c_functions_docs.t to
> 2. Have sent email to certain Parrot folk who can probably write better
> documentation than I have for certain files.
> 3. Awaiting feedback re 'memalign' files.
> 4. http://trac.parrot.org/parrot/ticket/1679 filed on basis of things
> observed doing this work.
> 5. Question: If the location at which I need to add documentation to a C
> function falls into the area between HEADERIZER_BEGIN and HEADERIZER_END --
> i.e., the area where you are told all changes will be lost -- how do I
> proceed without losing my additions? Relevant case:
> Thank you very much.
Michael H. Hind
Cell: +44 (0) 7877 224 745
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the parrot-dev