On Mar 16, 8:35 am, Rob Hamerling <[email protected]> wrote: > Hi Mike, > > On 03/16/10 12:11 am, m...@watty wrote: > > > lets not rush to update the current libraries till > > a) I finished fiddling with these :) > > Why don't you have your your files be validated by means of jallib.py > before committing? This is our way to enforce standards, or at least > consistency and sort of) quality control. > Your latest update of math.h for example contains lots of violations! > Since this library is in TORELEASE, it will be in the next release and > must adhere to the Jallib standards, be tested and have at least one > sample program demonstrating the functions and procedures. > > Regards, Rob. > > -- > Rob Hamerling, Vianen, NL (http://www.robh.nl/)
I'm writing these functions for my Catpad gadget. I don't think people need sample programs for sin, cos, fixed point multiply or PolarToCartesian. I don't want to maintain two sets of libraries. So if the "community" wants all lower case names for procedures and functions with underlines instead of camel case, someone else will have to copy changes from my libraries to the "Community Libraries". I'm never going to use polar_to_cartesian() in my own software, but PolarToCartesian() I've been using Camel Case for 25 years and only "_ " in CONSTANTS or where extra readability is needed. I last had a computer with no shift key in 1980. I'm sure a version of the validate tool could automatically make "PolarToCartesian ()" or "PolarToCartesian()" --> "polar_to_cartesian()" everywhere if that is what the "community" insists "official" libraries must have. -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
