When creating your own exceptions, I strongly recommend storing the data that caused the exception on the exception object itself. This greatly aids in debugging, especially in a well tested environment.

Example:

class MyError < StandardError
attr_accessor :some_object, :some_operation
def initialize(object, operation)
@some_object, @some_operation = object, operation
super("Failed to perform #{operation} on #{object}")
end
end

You can even use these error classes as domain events, and avoid raising them in a raise free architecture.

I write what I am learning and what I am thinking about as well as about anything else I find interesting. Some of it you can find in books and online (possibly because I read books as well as the web :)), other stuff is my own opinions and ideas. I post it all to various places so that other people have a chance to read it too, but only if they want to :).

I’ll keep blogging about ruby basics, and once I run out of basics, about more advanced stuff, after that we’ll see, because right now that is what I am finding interesting.

Yeah, rescuing Exception is no good whatever language you’re using. Although I can see how this could be particularly bad with Ruby (with Java I sometimes do this just so I can re-throw it as a RuntimeException :)).

I didn’t even know about the fact that you could use the retry keyword to run a begin block again, that is definitely handy.

This is I think the real value in blogging, when people come along and add to and expand on what you’ve written, to increase your knowledge and help anyone else who reads it later.

regards,
Gen.lostwarrior