From: John Carter Date: 2003-01-16T09:22:14+09:00 Subject: Re: 1.8.0 Preview & Test::Unit 0.1.6 On Wed, 15 Jan 2003, Nathaniel Talbott wrote: > Yup, I just noticed these last night. Unfortunately, Object#object_id > doesn't even exist in the 1.6 line (at least not 1.6.7), so I'm trying to > figure out what to do. I don't really want to maintain two Test::Unit > codebases, but that may be the only way to get around it. Here is another one for you I have just found. Running a unit test with ruby -d I get... Exception `NameError' at /usr/local/ruby-1.8.0/lib/ruby/site_ruby/1.8/test/unit.rb:164 - uninitialized constant DEBUGGER__ /usr/local/ruby-1.8.0/lib/ruby/site_ruby/1.8/test/unit.rb:164: uninitialized constant DEBUGGER__ (NameError) from /usr/local/ruby-1.8.0/lib/ruby/site_ruby/1.8/test/unit.rb:162 Which comes from this line in unit.rb # We can't debug tests run with at_exit unless we add the following: set_trace_func DEBUGGER__.context.method(:trace_func).to_proc if $DEBUG John Carter Phone : (64)(3) 358 6639 Tait Electronics Fax : (64)(3) 359 4632 PO Box 1645 Christchurch Email : john.carter@tait.co.nz New Zealand Good Ideas: Ruby - http://www.ruby-lang.org - The best of perl,python,scheme without the pain. Valgrind - http://developer.kde.org/~sewardj/ - memory debugger for x86-GNU/Linux Free your books - http://www.bookcrossing.com Memtest86 - http://www.memtest86.com - Free standalone, excellent memory tester for PC's.