cond 0.2.0 → 0.2.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- data/README +1 -1
- data/cond.gemspec +1 -1
- metadata +1 -1
data/README
CHANGED
|
@@ -85,7 +85,7 @@ called.
|
|
|
85
85
|
|
|
86
86
|
Cond is 100% compatible with the built-in exception-handling system.
|
|
87
87
|
We may imagine that Ruby had this handler/restart functionality from
|
|
88
|
-
very
|
|
88
|
+
the very beginning, but everyone had forgotten to write restarts. And
|
|
89
89
|
since no restarts were available, no handlers were written.
|
|
90
90
|
|
|
91
91
|
== Background
|
data/cond.gemspec
CHANGED
|
@@ -6,7 +6,7 @@ Gem::Specification.new { |t|
|
|
|
6
6
|
t.name = "cond"
|
|
7
7
|
t.rubyforge_project = t.name
|
|
8
8
|
t.homepage = "#{t.name}.rubyforge.org"
|
|
9
|
-
t.version = "0.2.
|
|
9
|
+
t.version = "0.2.1"
|
|
10
10
|
t.description = <<-EOS
|
|
11
11
|
+Cond+ allows errors to be handled at the place where they occur.
|
|
12
12
|
You decide whether or not the stack should be unwound, depending on
|