At 10:44 PM -0700 10/25/02, Brent Dax wrote:
I was thinking in terms of what TYPE: stores; it seems you were thinking
about how you identify a particular segment.  Yeah, you can probably get
away with just numbering the segments, although that might slow things
down a bit when you're looking for a particular type of segment.  (In
foo.pbc, the line location segment might be 1, but in bar.pbc, it's 2.)
Well, on thinking a bit about this, there's no reason that we have to worry--it's perfectly OK for us to declare, unconditionally, that segment 0 is always bytecode, 1 line number info, and so on, with everything after position X (for some value of X) left up in the air. A bit dodgy, true, as it means that any new known segment types we add in will be floating, but I don't think we're going to end up with too many performance-critical pieces in the bytecode. (Arguably it's just the bytecode itself, the symbols, and the constants, as the rest are looked at under exceptional circumstances or on (rare) demand)
--
Dan

--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk


Reply via email to