> Good to see some life back on this project! Today I adapted > i2c_hw_slave to work with jallib and created a timer-0 lib (for fixed > interval ISR). Not yet ready to add to jallib but it is in the > process!
Great ! Is this a state machine implementation ? I've implemented a i2c hw slave, and I'm very curious to know how you'd deal with that as a library. > As forETP: my idea is to forget about testing the library suite. Test > what you are working on as far as it is possible. Ask someone else if > you concider testing on a certain configuration is mandatory. Then > release and respond to user feed back. No feedback means it's good > enough. I second this. Yeah, ETP is utopia :) > > And on specific files: > > Only in unvalidated/include/jal: now.jal > Seems to be a special file. It defines the setting for a specific > application and I don't know if it should be included as a lib. I > think there should be a way to put this in the application program > itself. And if it is only a default, it could be in the lib itself... I remember we (Eur and I) had a discussion about this, I'll have a look. > Only in unvalidated/include/peripheral/i2c: i2c_level1.jal > Should be added. > It is better to use this level1 routine then the level0 routines it > calls. How can we notify users of this? Maybe we should not add the > level0-based examples. Then just put level1 lib in validated (I mean, keeping validated may still be useful). BTW, what are level 0 and level 1? > How about generating samples from test/board files? Is this still > concidered a real option? I seem the only one working with this > setup... I still think this is a good idea. I'd like to use them. And I still have to add some automation to generate all samples for all PICs. Question: when I have time to write my GP2D02 lib, should I add the test as a test file ? Or is it too a specific part ? I mean, should we only consider using board/tests => samples for core lib, or for every lib ? 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 -~----------~----~----~----~------~----~------~--~---
