> 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?
This is the debate we have about "not duplicated code" vs. "ready to compile" approach. "not duplicated code" approach is better by design but add complexity users may find to overkill. On the contrary, "ready to compile" samples approach is simple, but... well... may produce duplicated code ! Since it's not just a matter of "include 16fxxx" statement (need to define pragma which can differs amongst different), AFAIK there's no generic, simple, efficient compromise... This is of course open to debate, if you have any suggestions... You can have a look at http://code.google.com/p/jallib/wiki/UnderstandingSvnStructure for a little more about the current sample and tests maps. One way to know which samples are available for a given lib is to look at jalapi documentation: once regenerated, you'd see a link to all samples which uses this lib. Maybe that's "too far". I mean, user needs too much clicks to get these results. I could create/generate another page to summarize all lib <=> samples usage. 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 -~----------~----~----~----~------~----~------~--~---
