Hi Seb, On May 6, 1:14 am, Sebastien Lelong <[email protected]> wrote: > > I do have another compromise, which keeps init procedure split, but produce > the exact same HEX code, that is, same md5sum. This would, on the other > side, consume more memory for program using SD Card for instance. This > involves removing "inline" from spi_init() and move it set_mode(). >
Yes! This is what I thought was your original intent, when you said you had verified that the HEX code was the same, and is why I kept asking about the inline statements and their placement. As to why you wanted to rewrite spi_init to use your new routines, I have no idea. Perhaps you thought it was more elegant, or more efficient, or??? As your latest compromise proves, the HEX code will be exactly the same. Now then, about open-source -- JALLIB is 'released' every so often, correct? And those 'releases' do not require the end-user to know anything about SVN, so it is important that each source file in the 'release' adhere to the copyright and license of each individual source file. That is why I wanted you to add your name to the files, and remove my name from a file that I didn't create. As the author of the library, which is in fact the very heart of hardware SPI operation, I do intend to speak up from time to time. 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.
