armin-joellenbeck-rdbc 0.2.4 → 0.2.5

data/README.rdoc

@@ -1,4 +1,4 @@
-=Design by Contract for Ruby
+=Rdbc -- Design by Contract for Ruby
 
 This library supports Design by Contract for Ruby.
 
@@ -10,20 +10,15 @@ Install the *rdbc* gem itself by the following command:
 
 =Usage
 
-A a standard example for Design by Contract consider the following Stack
-class and its contract StackContract.
-
-  :include:spec/stack_spec.rb
-
-The mechanics are really simple. There is the class Stack.
+Given there is a the class Foo.
 For instances of this class you can define a contract by subclassing
-<b>DesignByContract::Contract</b>, in the example the contract is named
-StackContract.
-Then connect the class Stack to its contract StackContract by using the line
-  contract StackContract
-in the class definition of Stack.
+<b>Rdbc::Contract</b>, in the example the contract is named
+FooContract.
+Then connect the class Foo to its contract FooContract by using the line
+  contract FooContract
+in the class definition of Foo.
 
-Then the following happens when a method of a Stack instance is called:
+Then the following happens when a method of a Foo instance is called:
 
 1. the corresponding pre condition is called with the parameters:
    * the instance itself
@@ -44,11 +39,7 @@ Then the following happens when a method of a Stack instance is called:
 The instance before the execution of *method* in 3. and 4.
 is in fact a copy of the instance before the execution. So you have to implement
 the method *initialize_copy* in the class under contract, i.e. the class
-Stack.
-
-In any of these contract methods you can use assertions as in Test::Unit tests.
-When an assertion fails, the exception Test::Unit::AssertionFailedError
-is raised.
+Foo.
 
 =Support
 

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification 
 name: armin-joellenbeck-rdbc
 version: !ruby/object:Gem::Version 
-  version: 0.2.4
+  version: 0.2.5
 platform: ruby
 authors: 
 - Armin Joellenbeck