2011/5/6 William <[email protected]> > Another solution might be to copy the library to a new name, add make > all the changes you like. something like spi_master_hw_4g.jal ? Then > folks can choose whether they want to modify their libraries and > samples to use your new library instead of the original. >
<irony>Yes, that's an option, we could also create a SVN branch dedicated to William...</irony> Do you realize how messy our repository would become ? Again, do you think it's valuable for our project ? Don't you think users would get lost when choosing a library ?? I have another option to offer. Actually, to re-offer since you didn't want to reply to it previously. Here we go again: you want to use a specific version of spi_master_hw.jal, why don't you stick to a specific revision for this file (ie. r2585) ? When you get time and when you want, you'll be able to test the new version and finally upgrade your revision number to the one you recently tested. Please reply on this point. > > But those (like me) who have invested time and effort into testing the > original version, won't have to re-test. I'll ask Matt's question again here: when a new compiler is released, how do you manage this important change ? Do you ask Kyle not to change his compiler because you put a lot of time and energy of testing your programs and you don't want to re-test them ? Another important question: you may have noticed device files are evolving. Don't you feel you have to test your program again when new device files are release ? How do you manage this important change too ? Cheers, 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.
