Hi Matt, I can see the following comments (I changed 2.40 -- zero -- to 2.4o -- letter o--):
--for jalv2 2.4o ;var volatile byte sd_sector_buffer_low[256] -- 256 low bytes ;var volatile byte sd_sector_buffer_high[256] -- 256 high bytes -- --for jalv2 2.4n var byte sd_sector_buffer_low[256] -- 256 low bytes var byte sd_sector_buffer_high[256] -- 256 high bytes Ain't the "volatile" version work for both version ? We could also ask Kyle to add an internal compiler function used to identify current used version while compiling in order to react differently. Cheers, Seb 2011/5/2 <[email protected]> > Revision: 2621 > Author: [email protected] > Date: Mon May 2 13:10:52 2011 > Log: Added important note for incompatible compiler versions in lib. > put procedure was ok, but needed small optimization. > http://code.google.com/p/jallib/source/detail?r=2621 > > Modified: > /trunk/include/external/storage/sd_card/sd_card.jal > > -- 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.
