From: Asher Date: 2011-05-26T09:34:34+09:00 Subject: [ruby-core:36475] Re: Error reporting, backtraces and the debugger --Apple-Mail-12--502127843 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii I've implemented an objective backtrace and some other tools in Sender: = https://rubygems.org/gems/sender It currently works with 1.9.2. Asher On May 25, 2011, at 8:30 PM, Clifford Heath wrote: > (2) http://redmine.ruby-lang.org/issues/1906 by Run Paint Run Run >=20 > This issue requested that "caller" should be replaced (or augmented) = by a new method "backtrace" which yields an object-oriented backtrace. >=20 > It did not request that the same change be made to = Exception#backtrace, although the same name is suggested. (I find this = ommision strange). >=20 > Yehuda Katz mentions that Rubinius has an objectified backtrace. --Apple-Mail-12--502127843 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii https://rubygems.org/gems/sender=

It currently works with = 1.9.2.

Asher

On May 25, = 2011, at 8:30 PM, Clifford Heath wrote:

(2) http://redmine.ruby-lang= .org/issues/1906 by = Run Paint Run Run

This issue requested that "caller" should be = replaced (or augmented) by a new method "backtrace" which yields an = object-oriented backtrace.

It did not request that the same = change be made to Exception#backtrace, although the same name is = suggested. (I find this ommision strange).

Yehuda Katz mentions = that Rubinius has an objectified = backtrace.

= --Apple-Mail-12--502127843--