You're right, I should elaborate a bit on this. What I mean is that samples keep the same naming convention, which I now define as <device>_<sample_namespace>. I am restructuring the samples, so all <sample_namespace> samples only differ on device specific points and are all created by the same method. For instance, 18f4585_tmr0_poll_interval.jal was a manually generated sample, while all other '_tmr0_poll_interval.jal' are generated by jallib.py. As a result, the sample should have got another namespace (e.g. 18f4585_tmr0_poll_interval2.jal or any better name you can come up with) or be removed. For this particular sample, it was decided to remove this sample because there are already quite a few samples in this namespace and the added value for a sample for this chip does not make up for the maintenance burden of a manually maintained sample.
Regards, Joep 2014-03-04 14:48 GMT+01:00 mattschinkel <[email protected]>: > >2. only generate sampels with a 'namespace' (filename without the device > part) that is exclusively used by your methode? > > How would the device part get added again, and where would I put these > files? > > -- > You received this message because you are subscribed to the Google Groups > "jallib" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/jallib. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "jallib" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/jallib. For more options, visit https://groups.google.com/groups/opt_out.
