when I raise an exception inside a block being passed to a function, the outermost layer of my backtrace points to the line starting the function call, not the problematic line inside the block. Is there any way to augment that with more useful information?
sorry, I don't mean that my code intentionally raises an exception. I mean something further down in the call stack from my block raises it.
unfortunately I don't have the exact code that person is running, but I generally know what it looks like
it should look something like this: https://gist.github.com/andymeneely/d2bb2eb028b27cf1dace#file-_part2_01_factions-rb
I don't I have encountered this behavior myself as well, but don't have a test case handy. What's ahppening is that some library code is raising an exception somewhere inside the code block attached to Decknew(), and then the backtrace just calls out the deck.new() call instead of the line inside the block where the problem was.
right, but what line inside Deck.new() leads to the call to the call to the call to the call to layout_parser.rb?
I've got a ruby library. Users of the library install ruby, do `gem install foo`, then write a script that requires foo, then run their script. Is there an existing framework to package ruby, the library, and a gui editor/IDE with a "run script" button, all into one download?