Awesome stuff lads.
Perhaps this could be added to your .irbrc files to have it always present until backtraces are available?

That wouldn't do any good though, as __FILE__ and __LINE always point to the file and line of the binding that it's evaluated from. So putting it in .irbrc at line 3 would mean it would print ".irbrc: 3", not what you'd expect…

On 17/09/2009, at 7:20 PM, Matt Aimonetti wrote:

My understanding is that backtraces are really high on Laurent's TODO list and I also use the same trick as Vincent when I need to debug some of my code. (and yes, it's very frustrating and I can't wait to have some decent backtraces and hopefully a debugger)

- Matt

On Thu, Sep 17, 2009 at 1:23 AM, Vincent Isambart <vincent.isambart@gmail.com> wrote:

> Would it be possible for the error thrown to post some line / character
> information (backtrace?)

Adding backtrace information is in the TODO list for 0.5.

> Or can I turn some verboseness on for debugging these issues somehow?

Not currently. I tend to use a lot the following line when searching
for a MacRuby bug:
STDERR.puts "#{__FILE__}:#{__LINE}"

_______________________________________________
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

_______________________________________________
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

_______________________________________________
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel