Fri Oct 26 13:04:40 CEST 2007
next on are data buffers. i have some code that uses 14 byte buffers
together with some dirty trick of storing read/write pointers in one
byte for easy modulo addressing. i could dig that up again?
what is a buffer?
- 2 pointers: R/W
- base address of memory region (statically known)
- size (statically known)
suppose i represent it as 2 literal values: rw-var offset
see buffer.f for draft (committing now)
isn't it wise to write some code for generic 2^n buffers? where a
buffer consists of 2 variables, a mask indicating its size. ok, did
that but it leads to more verbose code.
a different strategy could be to store the read pointer or difference
at the point where W points, this saves a cell that's normally used to
distinguish between empty and full. hack for later..
anyways, i stick with the current: its probably good enough. i need to