kid51,<br><br>looks good to me, can't see anything glaringly obvious wrong.<br><br>If it passes the tests commit it. It is not as though it will break anything (famous last words).<br><br>Cheers, Michael (mikehh)<br><br>
<div class="gmail_quote">On 26 June 2010 16: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;">
<div class="im">James E Keenan 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>
</blockquote>
<br></div>
1. Deleted two files and some related code per comments from Andy Dougherty.<br>
<br>
2. Made what I thought were reasonable POD corrections to compilers/pirc/src/pircapi.c.<br>
<br>
3. Provided at least minimal documentation for remaining C functions.<br>
<br>
Can we get some eyeballs on the attached patch? If it's satisfactory (with or without content modifications), then I can merge the cfunctionsdocs into trunk. From that point forward, any failures in t/codingstd/c_function_docs.t will represent new C functions added to the repository without documentation.<div>
<div></div><div class="h5"><br>
<br>
Thank you very much.<br>
kid51<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Michael H. Hind<br><br>Cell: +44 (0) 7877 224 745<br>