Project

hammertime

0.07
No commit activity in last 3 years
No release in over 3 years
When this library is required, it replaces the default Ruby exception-raising behavior. When an error is raised, the developer is presented with a menu enabling them to ignore the error, view a stack trace, debug the error using IRB or ruby-debug, and more.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Development

>= 1.2.9

Runtime

~> 1.5
~> 0.10
 Project Readme

hammertime¶ ↑

An interactive error console similar to those found in Lisp and Smalltalk environments.

Synopsis¶ ↑

Simply require the Hammertime library:

require 'hammertime'

$broken = true

def faulty_method
  raise "Oh no!" if $broken
end

3.times do |n|
  puts "Attempt (#{n+1}/3)"
  begin
    faulty_method
    puts "No error raised"
  rescue => error
    puts "Error raised: #{error.inspect}"
  end
end

When an error is raised, a menu of possible actions will be presented at the console:

=== Stop! Hammertime. ===
An error has occurred at example.rb:4:in `raise_runtime_error'
The error is: #<RuntimeError: Oh no!>
1. Continue (process the exception normally)
2. Ignore (proceed without raising an exception)
3. Permit by type (don't ask about future errors of this type)
4. Permit by line (don't ask about future errors raised from this point)
5. Backtrace (show the call stack leading up to the error)
6. Debug (start a debugger)
7. Console (start an IRB session)
What now?

This enables a fix-and-continue style of development:

$ ruby example.rb                                                
Attempt (1/3)

=== Stop! Hammertime. ===
An error has occurred at example.rb:6:in `faulty_method'
The error is: #<RuntimeError: Oh no!>                   
1. Continue (process the exception normally)            
2. Ignore (proceed without raising an exception)        
3. Permit by type (don't ask about future errors of this type)
4. Permit by line (don't ask about future errors raised from this point)
5. Backtrace (show the call stack leading up to the error)              
6. Debug (start a debugger)                                             
7. Console (start an IRB session)                                       
What now?
7

>> $broken = false
=> false
>> exit

1. Continue (process the exception normally)
2. Ignore (proceed without raising an exception)
3. Permit by type (don't ask about future errors of this type)
4. Permit by line (don't ask about future errors raised from this point)
5. Backtrace (show the call stack leading up to the error)
6. Debug (start a debugger)
7. Console (start an IRB session)
What now?
2
No error raised
Attempt (2/3)
No error raised
Attempt (3/3)
No error raised

Known Bugs¶ ↑

  • Hammertime cannot intercept exceptions which are raised from native code.

TODO¶ ↑

  • Better integration with IRB to enable a “Retry” option.

  • Start console/debugger at fail site, instead of in Hammertime code.

  • Tests

Copyright © 2010 Avdi Grimm. See LICENSE for details.