Re: possible bug: stack dump with <<-String, #{...} and large loops

Hi,

At Wed, 29 May 2002 18:17:58 +0900,
ts wrote:
> n> I can imagine the only way [ruby-core:00053].  Otherwise,
> 
>  No, no [ruby-core:00053] or [ruby-core:00043] will not work. There is a
>  very good reason for the use of
> 
>     
>     ruby_eval_tree = block_append(ruby_eval_tree,
> 				  NEW_DASGN(0, NEW_LIT(0)));

But it means to push a dummy dvar *after* the expression.
[ruby-core:00053] pushes a dummy dvar *before* NODE_DSTR etc.

>  If I'm right ruby just need to test if the number of local variable was
>  modified before executing the nodes (i.e. just after the label default: in
>  NODE_DSTR). If this is true it must reallocate ruby_scope->local_vars and
>  perhaps remake 'ruby_scope->local_tbl = node->nd_tbl'

How about variables defined in eval?

-- 
Nobu Nakada