Dear Seb, Thank you for your tests. I'll try and do some CAN tests also.
On May 6, 6:14 pm, Sebastien Lelong <[email protected]> wrote: > > William, you didn't reply about sticking to a certain SVN revision. I think > this is a serious option considering your "freezing" approach. I hope you'll > find time to reply to this important point. > Actually I did, but I'll try again. End-user's don't use SVN, so specific revisions wouldn't be available to them. So my answer is no. > > 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 ? > I had assumed this was a rhetorical question, given my previous efforts to get Kyle to publish his code online, set up bug tracking, etc. Sure, I welcome better compilers. > > 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 ? Yes, I develop using 'trunk' and update from svn frequently. William -- 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.
