Re: [ ruby-Bugs-4151 ] Stack trace doesn't include class

On Wed, 19 Apr 2006, Eric Hodel wrote:

> > 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.

If it were only a matter of disambiguating, then the name of the method 
would be useless 99% of the time.

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

Then the object's class is not the object's class, and the method that 
belongs to an object really belongs to the object's singleton class 
because methods can't really belong to objects, and then the object's 
singleton class is sometimes seen as the object's class except when it's 
not. (Ruby is misleading already.)

You don't *have* to read the word "class" the wrong way. It doesn't always 
mean a non-singleton class and it doesn't even always mean an instance 
of the Class class. it can be a non-Class Module too, because modules 
are those second-class citizens that work the same way classes do 
except that they don't have the right to sit down when they take the 
bus.

 _ _ __ ___ _____ ________ _____________ _____________________ ...
| Mathieu Bouchard - t駘:+1.514.383.3801 - http://artengine.ca/matju
| Freelance Digital Arts Engineer, Montr饌l QC Canada