Jim Jagielski wrote:
OK, I think having 2 more API functions rounds out the impl; Consider: the current assumption is that the user manages the indexes into the slotmem. But what if the user doesn't?
Then he can't use the stuff :-(
Certainly it would make sense for the slotmem to know what slots are now currently available and return a "free" slot to the caller. So I think a "grab" and a "return" function are required as well.
I have malloc() / free() / getused() / getfree() switchable logic that I can add quickly. Basically it create a table of used and free slotmem additionally to data it.
Cheers Jean-Frederic
