On 2013-05-31, at 01:30, Greg King wrote: >> I mean, in the modern machine, a few KiBs here or there doesn't make >> any real difference; but, for a CBM, almost 16KiB for the buffer alone >> is a high price. > > Oh. I didn't realize that you "had gone native". ;-) :-) Well - "had gone" part is a bit of overstatement ;-) but - right - I don't want to make any design choices that would exclude such possibility in the end, once all the concepts are eventually ironed out. > How long is gcrBytes? Theoretically up to 64KiB but I take it to be no longer than about 8KiB (one 1541 track) and I bail out if it happens to be bigger. >> So far, I did this for the SYNC: >> [...] >> which, I believe, takes care of the wrapping, in a relatively effective way. > > What about a "compromise"? Mirror the first two bytes. Then, you would need to wrap-around the search; but not the 10-bit examination. Now that's a nice idea indeed! It can possibly save some bytes - good hint. -- SD! Message was sent through the cbm-hackers mailing listReceived on 2013-05-31 11:01:20
Archive generated by hypermail 2.2.0.