--- Comment #4 from David Simcha <> 2009-11-01 11:49:58 PST ---
1.  I chose to store the bitmask after SENTINEL_POST so that none of the
assumptions of the sentinel code (such as that the sentinel is immediately
after the data) changes.

2.  The fact that setBitMask() is a nested function is a minor holdover from
when the design was a little different.  If anyone really hates it a lot, it
can be refactored.

3.  The mixin is because I needed a lot of the same logic in realloc() and
extend() and it was complicated enough that I felt it was the lesser of two
evils to use a mixin, even with the "variables appearing out of nowhere" magic,
rather than duplicate that logic.

Configure issuemail:
------- You are receiving this mail because: -------

Reply via email to