Sebastien Lelong wrote:
> This sample should be stored in in sample/by_device/16f88 map, since
> it includes a "include 16f88" statement (one of the differences
> between a test and a sample, a test code being target chip
> independent).
Ah, now I understand why there are so few programs in 'test'!
OK, I see the difference and have moved and renamed it.
But this brings up another point. Many sample programs will work for
many other PICs with only a different device file. While now it may seem
that the program works only for a 16F88.
How will a user of another PIC find it if he is not
specifically/accidentally looking in the 16f88 directory?
> BTW could serial_hw_int_cts.jal lib be based on existing
> serial_hardware.jal one, or would it be overkill (stack problem, no
> overlap or not enough relevant overlap) ?
I didn't look in serial-hardware.jal until a few moments ago. On first
sight I don't think it is very useful, but it has some facilities that
could be useful. Maybe good for future enhancement.
Regards, Rob.
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
-~----------~----~----~----~------~----~------~--~---
