From: "James M. Lawrence" Date: 2011-02-02T14:36:09+09:00 Subject: [ruby-core:35041] [Ruby 1.9-Bug#4352] [patch] Fix eval(s, b) backtrace; make eval(s, b) consistent with eval(s) Issue #4352 has been updated by James M. Lawrence. Thank you for that detailed explanation. The problem for me is the connection to source_location, which should be usable by tools. Shouldn't source_location give the file and line of a method or block definition? If so then source_location is bugged when the binding argument is passed. The seemingly simplest solution is to make the backtrace and source_location consistent. It only takes a 4-line patch. I might have thought otherwise if virtual line numbers served some human purpose, but I just see them as confusing. Tools are even more confused. Should a new bug for source_location be created? ---------------------------------------- http://redmine.ruby-lang.org/issues/show/4352 ---------------------------------------- http://redmine.ruby-lang.org