> Finally, names are extremely important. We who have some experience with
> the code are one thing. People with less knowledge who need to use the API
> are another thing. The names should be as unambiguous, clear, and
> indicative of function as possible, consistent with being reasonably short.
> Actually, even the people who think they know the code will be benefit from
> renaming things as clearly as possible. Unclear names hide design problems.

Of course. I have given the precedence to the body of the functions
because it is the hardest work. Function rename is trivial.

In general, I won't add a comment to the API because it is the
documentation for the user and my words are unclear.

tito

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net