kid51,<br><br>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.<br><br>Who is our HEADERIZER guru, petdance++ I believe?<br><br>Cheers, Michael (mikehh)<br>
<br><div class="gmail_quote">On 13 June 2010 18:14, James E Keenan <span dir="ltr"><<a href="mailto:jkeen@verizon.net">jkeen@verizon.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Status of efforts in cfunctionsdocs branch:<br>
<br>
1. Have reduced number of files failing t/codingstd/c_functions_docs.t to 3.<br>
<br>
2. Have sent email to certain Parrot folk who can probably write better documentation than I have for certain files.<br>
<br>
3. Awaiting feedback re 'memalign' files.<br>
<br>
4. <a href="http://trac.parrot.org/parrot/ticket/1679" target="_blank">http://trac.parrot.org/parrot/ticket/1679</a> filed on basis of things observed doing this work.<br>
<br>
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: compilers/pirc/src/pircapi.c.<div>
<div></div><div class="h5"><br>
<br>
Thank you very much.<br>
<br>
<br>
kid51<br>
<br>
_______________________________________________<br>
<a href="http://lists.parrot.org/mailman/listinfo/parrot-dev" target="_blank">http://lists.parrot.org/mailman/listinfo/parrot-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Michael H. Hind<br><br>Cell: +44 (0) 7877 224 745<br>