On 03/30/10 07:37 am, vasile surducan wrote:
Contributions should be run through validation by the contributor
himself before committing. The tools are available to anyone. Code
which does not validate should be put aside.
I understand by validation two steps:
1. the code is tested on the contributor's hardware and works
2. the code met the rules of jallib
There isn't other step right?
The first is a matter of trusting people. We don't always want (to spend
time) to check the working of a library. And we cannot always check, for
example when it uses external devices we don't have.
There must be at least one sample using the functions/procedures of a
library: (1) as an example how to use each of the functions and
procedures (2) for regression tests with new compiler, new device files,
changes in other libraries (e.g. frequently included libraries like jal,
format, print).
A library must be generally usable, preferrably with all PICs supported
by JalV2. If this is not possible it must have a 'protection' against
misuse, e.g. an error message like
"<this library> cannot be used in combination with <this PIC>".
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.
