[#1] Welcome to the ruby-core mailing list — matz@... (Yukihiro Matsumoto)
Hi,
2 messages
2002/05/10
[#7] Useless patch... — Michal Rokos <m.rokos@...>
Hi,
6 messages
2002/05/14
[#19] Re: [BUG] thread failure after trap — nobu.nokada@...
Hi,
11 messages
2002/05/16
[#20] Re: [BUG] thread failure after trap
— ts <decoux@...>
2002/05/16
>>>>> "n" == nobu nokada <nobu.nokada@softhome.net> writes:
[#23] Re: [BUG] thread failure after trap
— nobu.nokada@...
2002/05/16
Hi,
[#42] Re: possible bug: stack dump with <<-String, #{...} and large loops — ts <decoux@...>
32 messages
2002/05/25
[#43] Re: possible bug: stack dump with <<-String, #{...} and large loops
— nobu.nokada@...
2002/05/26
Hi,
[#45] Re: possible bug: stack dump with <<-String, #{...} and large loops
— ts <decoux@...>
2002/05/26
>>>>> "n" == nobu nokada <nobu.nokada@softhome.net> writes:
[#46] Re: possible bug: stack dump with <<-String, #{...} and large loops
— nobu.nokada@...
2002/05/26
Hi,
[#47] Re: possible bug: stack dump with <<-String, #{...} and large loops
— ts <decoux@...>
2002/05/26
>>>>> "n" == nobu nokada <nobu.nokada@softhome.net> writes:
[#48] Re: possible bug: stack dump with <<-String, #{...} and large loops
— ts <decoux@...>
2002/05/26
>>>>> "t" == ts <decoux@moulon.inra.fr> writes:
[#49] Re: possible bug: stack dump with <<-String, #{...} and large loops
— nobu.nokada@...
2002/05/27
Hi,
[#50] Re: possible bug: stack dump with <<-String, #{...} and large loops
— ts <decoux@...>
2002/05/27
>>>>> "n" == nobu nokada <nobu.nokada@softhome.net> writes:
[#51] Re: possible bug: stack dump with <<-String, #{...} and large loops
— nobu.nokada@...
2002/05/27
Hi,
[#52] Re: possible bug: stack dump with <<-String, #{...} and large loops
— ts <decoux@...>
2002/05/27
>>>>> "n" == nobu nokada <nobu.nokada@softhome.net> writes:
[#53] Re: possible bug: stack dump with <<-String, #{...} and large loops
— nobu.nokada@...
2002/05/27
Hi,
[#54] Re: possible bug: stack dump with <<-String, #{...} and large loops
— ts <decoux@...>
2002/05/27
>>>>> "n" == nobu nokada <nobu.nokada@softhome.net> writes:
[#55] Re: possible bug: stack dump with <<-String, #{...} and large loops
— nobu.nokada@...
2002/05/27
Hi,
[#56] Re: possible bug: stack dump with <<-String, #{...} and large loops
— ts <decoux@...>
2002/05/27
>>>>> "n" == nobu nokada <nobu.nokada@softhome.net> writes:
[#57] Re: possible bug: stack dump with <<-String, #{...} and large loops
— nobu.nokada@...
2002/05/28
Hi,
[#65] Re: possible bug: stack dump with <<-String, #{...} and large loops
— ts <decoux@...>
2002/05/28
>>>>> "n" == nobu nokada <nobu.nokada@softhome.net> writes:
[#84] Re: possible bug: stack dump with <<-String, #{...} and large loops
— nobu.nokada@...
2002/05/29
Hi,
[#92] Re: possible bug: stack dump with <<-String, #{...} and large loops
— ts <decoux@...>
2002/05/29
>>>>> "n" == nobu nokada <nobu.nokada@softhome.net> writes:
[#93] Re: possible bug: stack dump with <<-String, #{...} and large loops
— nobu.nokada@...
2002/05/29
Hi,
[#94] Re: possible bug: stack dump with <<-String, #{...} and large loops
— ts <decoux@...>
2002/05/29
>>>>> "n" == nobu nokada <nobu.nokada@softhome.net> writes:
[#95] Re: possible bug: stack dump with <<-String, #{...} and large loops
— nobu.nokada@...
2002/05/29
Hi,
[#96] Re: possible bug: stack dump with <<-String, #{...} and large loops
— ts <decoux@...>
2002/05/29
>>>>> "n" == nobu nokada <nobu.nokada@softhome.net> writes:
[#59] yyparse() and friends >> rubyparse() or rbparse()... — Sean Chittenden <sean@...>
Would it be possible to add '-p ruby' to the bison command line args
8 messages
2002/05/28
[#60] Re: yyparse() and friends >> rubyparse() or rbparse()...
— matz@... (Yukihiro Matsumoto)
2002/05/28
Hi,
[#61] Re: yyparse() and friends >> rubyparse() or rbparse()...
— Sean Chittenden <sean@...>
2002/05/28
> |Would it be possible to add '-p ruby' to the bison command line
[#67] The warns-a-thon continues... — Sean Chittenden <sean@...>
I'm feeling left out in this race to clobber warnings!!! Attached are
19 messages
2002/05/28
[#69] Re: The warns-a-thon continues...
— matz@... (Yukihiro Matsumoto)
2002/05/28
Hi,
[#70] Re: The warns-a-thon continues...
— WATANABE Hirofumi <eban@...>
2002/05/28
Hi,
[#71] Re: The warns-a-thon continues...
— Sean Chittenden <sean@...>
2002/05/28
> :*) Fixed some sprintf() format type mismatches
[#86] rb_hash_has_key() and friends non-static... — Sean Chittenden <sean@...>
I'm doing a lot of work with Ruby in C and am using some of Ruby's
9 messages
2002/05/29
[#117] Re: rb_hash_has_key() and friends non-static...
— Sean Chittenden <sean@...>
2002/06/03
At the moment I'm writing an appendix Beginning Ruby Programming
[#119] Re: rb_hash_has_key() and friends non-static...
— nobu.nokada@...
2002/06/04
Hi,
[#104] Re: possible bug: stack dump with <<-String, #{...} and large loops — ts <decoux@...>
>>>>> "n" == nobu nokada <nobu.nokada@softhome.net> writes:
29 messages
2002/05/30
[#105] Re: possible bug: stack dump with <<-String, #{...} and large loops
— nobu.nokada@...
2002/05/30
Hi,
[#106] Re: possible bug: stack dump with <<-String, #{...} and large loops
— ts <decoux@...>
2002/05/31
>>>>> "n" == nobu nokada <nobu.nokada@softhome.net> writes:
[#107] Re: possible bug: stack dump with <<-String, #{...} and large loops
— nobu.nokada@...
2002/05/31
Hi,
[#125] Re: possible bug: stack dump with <<-String, #{...} and large loops
— ts <decoux@...>
2002/06/04
>>>>> "n" == nobu nokada <nobu.nokada@softhome.net> writes:
[#126] Re: possible bug: stack dump with <<-String, #{...} and large loops
— nobu.nokada@...
2002/06/04
Hi,
[#127] Re: possible bug: stack dump with <<-String, #{...} and large loops
— ts <decoux@...>
2002/06/04
>>>>> "n" == nobu nokada <nobu.nokada@softhome.net> writes:
[#130] Re: possible bug: stack dump with <<-String, #{...} and large loops
— nobu.nokada@...
2002/06/04
Hi,
[#132] Re: possible bug: stack dump with <<-String, #{...} and large loops
— nobu.nokada@...
2002/06/05
Hi,
[#134] Re: possible bug: stack dump with <<-String, #{...} and large loops
— ts <decoux@...>
2002/06/05
>>>>> "n" == nobu nokada <nobu.nokada@softhome.net> writes:
[#135] Re: possible bug: stack dump with <<-String, #{...} and large loops
— ts <decoux@...>
2002/06/05
>>>>> "t" == ts <decoux@moulon.inra.fr> writes:
[#138] Re: possible bug: stack dump with <<-String, #{...} and large loops
— matz@... (Yukihiro Matsumoto)
2002/06/05
Hi,
Re: possible bug: stack dump with <<-String, #{...} and large loops
From:
nobu.nokada@...
Date:
2002-05-28 01:33:48 UTC
List:
ruby-core #57
Hi,
At Tue, 28 May 2002 00:56:00 +0900,
ts wrote:
> n> Another approach.
>
> Seems better,
Since it was too ugly, additional patch, and testcases. The
latest versions of 1.6 and 1.7 succeed the tests excepting
test_bug.
--- eval.c~ Mon May 27 23:34:52 2002
+++ eval.c Tue May 28 09:34:42 2002
@@ -3059,8 +3059,6 @@ rb_eval(self, n)
if (ruby_scope->local_tbl) {
NODE *body = (NODE *)ruby_scope->scope_node;
- if (body &&
- (!body->nd_tbl ||
- body->nd_tbl != ruby_scope->local_tbl &&
- (free(body->nd_tbl), 1))) {
+ if (body && body->nd_tbl != ruby_scope->local_tbl) {
+ if (body->nd_tbl) free(body->nd_tbl);
ruby_scope->local_vars[-1] =
(VALUE)(body->nd_tbl = ruby_scope->local_tbl);
--
Nobu Nakada
Attachments (1)
tc_evstr.rb
(824 Bytes, text/x-ruby)
require 'test/unit'
class TC_Evstr < Test::Unit::TestCase
def bug
"#{a=1}"
end
def bug2
"#{a = 12
2.times {b = 1}
'end'
a}"
end
def test_bug
assert_equal("1", assert_nothing_raised {bug})
assert_equal("1", assert_nothing_raised {bug})
assert_equal("12", assert_nothing_raised {bug2})
assert_equal("12", assert_nothing_raised {bug2})
end
def test_error
begin "#{a = b = 1:}"; rescue SyntaxError; end
assert_raises(NameError) {eval "a"}
assert_raises(NameError) {eval "b"}
end
def test_raise
begin "#{a = 1; raise}"; rescue; end
assert_equal("1", "#{a}")
end
def test_nest
"#{"#{a=1}"}"
assert_equal("1", "#{a}")
end
def test_dvar
"#{a = 12}"
eval "x = 12"
assert_equal("local-variable", "#{defined? x}")
end
end