Project

General

Profile

Actions

Feature #2824

closed

Backtrace from Singleton Classes is Unclear

Added by runpaint (Run Paint Run Run) about 14 years ago. Updated about 12 years ago.

Status:
Closed
Assignee:
-
Target version:
[ruby-core:28368]

Description

=begin
The backtrace from singleton classes needs a space between 'singleton' and 'class'.

$ ruby -e 'class << self; x; end'
-e:1:in singletonclass': undefined local variable or method x' for #<Class:#Object:0x83efde8> (NameError)
from -e:1:in `'

However, more useful would be to indicate which object's singleton class raised the exception. This is particularly relevant for exceptions whose messages do not include the caller's #inspect output. For example, compare:

$ ruby -e 'class H; 1/0; end'
-e:1:in /': divided by 0 (ZeroDivisionError) from -e:1:in class:H'
from -e:1:in `'

$ ruby -e 'class << "c"; 1/0; end'
-e:1:in /': divided by 0 (ZeroDivisionError) from -e:1:in singletonclass'
from -e:1:in `'
=end


Files

singleton-compile.c.patch (475 Bytes) singleton-compile.c.patch runpaint (Run Paint Run Run), 09/02/2010 11:45 PM
Actions #1

Updated by znz (Kazuhiro NISHIYAMA) almost 14 years ago

  • Target version set to 2.0.0

=begin

=end

Actions #2

Updated by runpaint (Run Paint Run Run) over 13 years ago

=begin
The attached fixes the typo; improving the error message appears to require knowledge of YARV internals.
=end

Actions #3

Updated by akr (Akira Tanaka) about 12 years ago

  • Status changed from Open to Closed
  • % Done changed from 0 to 100

This issue was solved with changeset r35079.
Run Paint, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.


Actions

Also available in: Atom PDF

Like0
Like0Like0Like0