Thaumato

I always forget this - being a java programmer originally I tend to think of things in java parlance when I’m looking for a way to do them in ruby. Right now I want to print the stack trace to the log in the enhancements to the merb uploader I’m doing, and, anyway - heres how you do it in ruby.

begin
some code
rescue Exception=>e
Merb.logger.error(e.backtrace.join("\n"))
end

Also - to get merb to log to a file make sure your settings are correct in init.rb or whichever env you are in.
i.e. c[:log_file] = Merb.root / “log” / “development.log”

Just wanted to post this, mostly since I just completely realized it myself after programming in Rails/Ruby for a couple of years. Amazing. Also, wanted to post something since this blog isn’t very bloggy. Also wanted to get this onto teh internet more - just in case some poor bastard out there is wondering, maybe this will save him 2 seconds. Who knows, it could add up. We all need to do what we can.

Anyway - in Ruby you cannot overload methods like you can in Java. Ruby won’t complain if you do, I believe it will just use the last implementation of the method it loaded. And when you pass the wrong type in, it will just blow up. This has been the hardest part for me, in transitioning to Ruby from Java. I still use Java for my day job and one nice thing about it is when something goes wrong the stack trace usually tells you exactly what caused it. Ruby’s stack trace has the answers as well, but you need to figure out exactly what you did wrong. Ruby will give you the rope and let you hang yourself. Ok its not that dramatic, just requires a different kind of debugging.