Hi guys,

Could we agree to prefix filename with "test_" ONLY for tests, *not* for
samples ?
Why ? While I'm working at the "jallib" script, you can easily register test
results, such as:

    jallib.py test -a 16f88:serial_hw_echo.jal:true
    jallib.py test -a 16f648a:test_serial_hardware.jal:true

(this will also automatically record the revision, if libs are installed,
btw)

In the first case, because the filename is not starting with "test_", it
knows it's a sample, thus it can reconstitute the sample path using
"by_device" + pic + filename.
In the second one, because it starts with "test_", it knows it'll have to
explore the "test_" map. If we allow samples to be prefixed with "test_",
then I'll need to handle this in "jallib", and this will make a more
complicated commandline.

I've seen there're few samples which start with "test_":

 * by_device/16f876a/test_sht.jal (Eur, is there a lib ?)
 * by_device/16f876a/test_tc77.jal
 * by_device/16f877a/test_display_hd44780_4_line.jal
 * by_device/16f877a/test_display_hd44780_8_line.jal


Can I (you) rename them ? Do you agree ?


Seb

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to