I don't believe that the optree has to be bloated. I think having the
actual line number in the optree vs. having a seperate structure
mapping offsets to line numbers are the same.
Then an error report would be akin to
error_me_this(current_op_address, "Foo didn't baz in time. Aborting")
Having the bloat in a seperate memory area lets it get swapped out
until absolutely necessary. And helps preseve locality for the optree.
<chaim>
>>>>> "DS" == Dave Storrs <[EMAIL PROTECTED]> writes:
DS> As to solving problem #1 (which is, arguably, the bigger problem),
DS> suppose we add a new switch to perl? I propose we add the -H switch
DS> (mnemonic: *H*elpful errors/warnings). When -H is set, the optree would
DS> be generated with a sufficient amount of bloat that it could report the
DS> errors/warnings at the exact spot they occur, even down to reporting the
DS> appropriate failure line in a multiline statement. We don't worry about
DS> bloat or slowdown, because the assumption is that -H is only used during
DS> debugging or when speed doesn't matter, and it will be turned off when the
DS> code goes to production.
--
Chaim Frenkel Nonlinear Knowledge, Inc.
[EMAIL PROTECTED] +1-718-236-0183
