uses('debugger');
And now you get all the data you need when something goes wrong, and right within your browser.
One thing that is lacking though, that I would really like to see, is the option to output the debugging results to a log file instead. As outputting to the browser can be very messy. I have already opened a ticket with this suggestion, so hopefully the core team will add that.
This site contains the musings of Joel Moss, and is powered by Codaset pages; a simple, yet powerful way to host your static site. Just commit and push your site to your free Git repository at Codaset, and that's it!
Related Articles...
- Quick and easy emailing in Ruby with Pony
- Concerned with Rails
- Codaset Opens up its Beta to Everyone.
- Railings: A full featured Ruby on Rails template
- CSS Pick and Mix Classes
- A sexy, ajax based jQuery dialog window, with a one track mind.
- Codaset is alive!
- 10 Reasons why Ruby is better than PHP - Reason #5
- 10 Reasons why Ruby is better than PHP - Reason #4
- 10 Reasons why Ruby is better than PHP - Reason #3
