ED</span></a>), and is really very
terribly awfully weird, so we map the values to iPodDB specific values with
the high bit set.
</p>
<p>
On writing, we check the high bit and write the limitsort_opposite from that.
That way, we don't have to deal with programs using the class needing to set
the wrong limit and then make it into the "opposite", which would be frickin'
annoying.
</p>
<div class="variablelist"><table border="0" class="variablelist">
<colgroup>
<col align="left" valign="top">
<col>
</colgroup>