<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div apple-content-edited="true">Original PM3 scheme is a bit too much back :), being non OO. Objectness of TEXT has its uses.
</div><div apple-content-edited="true"><br></div><div apple-content-edited="true">I think your scheme can be incorporated as an alternative, selectable during m3core build, without much problem. I would like to try it.</div>
<br><div><div>On Apr 26, 2013, at 9:37 PM, Rodney M. Bates wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Candara; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">I posted a bunch of empirical performance numbers on this list, showing some of the tradeoffs<br>of my intermediate implementation. I think it would represent a good middle ground. Barring<br>that, I too would go back to the PM3 scheme, as the storage use and access time of the original<br>CM3 scheme can be pretty awful.</span></blockquote></div><br></body></html>