On Apr 17, 2006, at 1:11 PM, noreply / rubyforge.org wrote:

> Bugs item #4151, was opened at 2006-04-17 23:10
> You can respond by visiting:
> http://rubyforge.org/tracker/? 
> func=detail&atid=1698&aid=4151&group_id=426
>
> Category: None
> Group: None
> Status: Open
> Resolution: None
> Priority: 3
> Submitted By: Oren Ben-Kiki (oren)
> Assigned to: Nobody (None)
> Summary: Stack trace doesn't include class
>
> Initial Comment:
> The stack trace provided by the Ruby engine uses a hard-wired  
> template including the source file name, line number and the name  
> of the method. For some reason, it doesn't contain the name of the  
> class containing the method.

I don't understand how just a file name and line number are ambiguous  
when reading a backtrace.

> A lot of Ruby functionality is provided as extensions to the  
> standard library, where it makes sense to have one file per class  
> (more or less). This compensates for the above lack to a great extent.
>
> However, it also makes sense to write straight scripts in Ruby. In  
> my case, quite an involved script that contains many classes, but  
> is still a single file I can easily distribute to users etc. In  
> this case, the lack of the class name in the stack trace is rather  
> limiting.

Adding the class may be misleading.  A method may belong to an object  
but not the object's class.

-- 
Eric Hodel - drbrain / segment7.net - http://blog.segment7.net
This implementation is HODEL-HASH-9600 compliant

http://trackmap.robotcoop.com