On 14 Sep 2008, at 13:50 , [EMAIL PROTECTED] wrote: > > Issue 24: Migration: i2c > http://code.google.com/p/jallib/issues/detail?id=24 > > Comment #7 by jsuijs: > First version of i2c_software is there. When adding to the tree, I > was in > doubt > where to put this. > Since it is a language extension, I put it in \jal. But one could > argue it
which is OK. > is for > external devices and put it in \external. A LED is external too. > A next file, which uses i2c_* to > read/write to an i2c eeprom belongs there. It does. > And then there is i2c_hardware, which is a perpheral lib. OK. > As a result, the three files I intend to deliver all have their own > place. > Is this > what we want or do we want to keep it together, since they are so > closely > related? Yes, IMHO. Keep in mind that all libs will be thrown on a heap when releasing. > > Joep > > > > -- > You received this message because you are listed in the owner > or CC fields of this issue, or because you starred this issue. > You may adjust your issue notification preferences at: > http://code.google.com/hosting/settings > > > > --- ir EE van Andel [EMAIL PROTECTED] http://www.fiwihex.nl Fiwihex B.V. Wierdensestraat 74, NL7604BK Almelo, Netherlands tel+31-546-491106 fax+31-546-491107 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
