On 03/16/10 09:52 am, m...@watty wrote:
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.
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.
The Jallib group decided to we should have a sample for everything.
This is not only for users to show how to use functions and procedures,
but also as a (sort of) proof that all functions and procedures compile
(with current and new compiler versions).
I don't want to maintain two sets of libraries.
You don't have to: throw away your libraries and use Jallib.
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".
Everybody here does the 'dirty' work himself.
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.
What you do for yourself is completely up to you, what you want to do
for Jallib has to meet the Jallib conventions.
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.
Everything is possible, but somebody has to do it, why not you?
Regards, Rob.
--
Rob Hamerling, Vianen, NL (http://www.robh.nl/)
--
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.
