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

Hi,

# may misunderstand what you mean...

At Mon, 27 May 2002 17:51:09 +0900,
ts wrote:
> n> +	    if (!ruby_dyna_vars) rb_dvar_push(0, 0);
> 
>  If ruby fail and the user has protected the call via (begin ... rescue)
>  ruby will think that it's in a dynamic scope.
> 
>  This is why I've tried to protect it with PUSH_TAG() ...

Since begin/rescue doesn't separate variable scope, dynamic
variables defined in it should be accessible after it.

  begin "#{a=1; raise}"; rescue; end
  p "#{a}"

[ruby-core:00047] disposes only a dvar header, so the above
succeeds, but the following fails.

  "#{"#{a=1}"}"
  p "#{a}"

-- 
Nobu Nakada