Re: RFC 214 (v1) Emit warnings and errors based on unoptimized code

[Dan Sugalski]

At 05:21 PM 9/15/00 -0400, Chaim Frenkel wrote:
>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.

We can look to see which way works best. Putting line info into the optree 
is certainly simplest, but might not be the optimal solution. (Whether 
we'll have time for an optimal solution's another matter entirely...)

                                        Dan

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