At 1:08 PM -0800 10/27/02, chromatic wrote:
Nope, not really related. The engine may know about the source or line number information--certainly if it wants to emit meaningful error messages for the number chunk, or reparse the source for the former. (On the off chance that something changes significantly enough to warrant recompiling a segment of code) Debuggers might also make some use of that, though I don't suppose they have to.On Sun, 27 Oct 2002 08:54:08 -0800, Dan Sugalski wrote:These two seem highly similar:=item Add source code to segment This adds a line or more of source code to the bytecode segment.=item Add line number information
This adds line number info to the bytecode segment, allowing the interpreter
to find out what line of source a particular piece of bytecode corresponds to.
They might be related to this one, though I'm not completely sure: > =item Add binary data chunk to segment
Arbitrary metadata? Nope, no plans for that. While I can see it as a useful thing (though it wouldn't be unicode, at least unicode wouldn't be required) I'm not sure it's worth the time to define, implement, and maintain.Is there an underlying function used to add arbitrary (Unicode text) metadata to the bytecode?
On the other hand, if someone has a good proposal, clean API, and generally feels strongly about it I certainly won't have any objections.
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
