Greetings Seb, Your proposal looks good.
I'll defer to Matt and/or others about the use of inline. Personally I'd try to pick hardware that could all run at the same speed and mode and only call spi_init() once. You asked about headers, and I assume by that you mean the boilerplate for author, copyright, zlib, etc. So, I am answering here. I made some hasty remarks the past few days that I regret, and I ask forgiveness for that. My concerns for an author's copyright remains, but my conduct was poor. The future and long-term success of JALLIB is important to me. So, in (hopefully rare) cases like this, when the decision is made to replace an original work with a derived work, using the same filename, might help future situations like this if we did it somewhat formally. I am not sure exactly how to do this but I am thinking it would be something like: move my name and copyright further down in the header somewhere or in the comment section, and add your own name and copyright at the top of the file. This would, it seems to me, comply with the ZLIB clause #3. You probably had this in mind when you left my name as author of spi_master_hw2.jal and I regret my mis-handling of that. You all have obviously taken the SPI libraries far beyond what I needed, and clearly at this point (with your proposal) it is a 'derived work' and you deserve credit for that. 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.
