abstract_method 1.0.0 → 1.1.0
Sign up to get free protection for your applications and to get access to all the features.
- data/README.md +5 -7
- data/VERSION +1 -1
- metadata +5 -7
data/README.md
CHANGED
|
@@ -50,9 +50,9 @@ end
|
|
|
50
50
|
When called, the abstract method will raise an `AbstractMethodCalled` exception with a helpful message:
|
|
51
51
|
|
|
52
52
|
```ruby
|
|
53
|
-
AbstractClass.new.foo #
|
|
54
|
-
#
|
|
55
|
-
#
|
|
53
|
+
AbstractClass.new.foo # raises AbstractMethodCalled with the following message:
|
|
54
|
+
# Called unimplemented abstract method AbstractClass#foo
|
|
55
|
+
# (defined in class AbstractClass).
|
|
56
56
|
```
|
|
57
57
|
|
|
58
58
|
Abstract methods can be overridden as usual:
|
|
@@ -72,11 +72,9 @@ For more information, see the [API documentation](http://rubydoc.info/github/ope
|
|
|
72
72
|
FAQ
|
|
73
73
|
---
|
|
74
74
|
|
|
75
|
-
**Why define abstract methods? In a dynamic language like Ruby
|
|
75
|
+
**Why define abstract methods? In a dynamic language like Ruby they aren't needed.**
|
|
76
76
|
|
|
77
|
-
Mainly for documentation purposes.
|
|
78
|
-
|
|
79
|
-
Imagine writing a plugin system where the plugins are classes derived from one superclass. For a plugin author it would be great to see what methods plugins need to implement directly from the superclass code. The abstract method definition is also a great place to put documentation describing what the method should do.
|
|
77
|
+
Mainly for documentation purposes. The definitions allow subclass authors to easily see what they need to implement. They are also a great place to attach documentation.
|
|
80
78
|
|
|
81
79
|
**Why create a new library? There is already the [abstract](http://rubygems.org/gems/abstract) gem.**
|
|
82
80
|
|
data/VERSION
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
1.
|
|
1
|
+
1.1.0
|
metadata
CHANGED
|
@@ -1,13 +1,13 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: abstract_method
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
hash:
|
|
4
|
+
hash: 19
|
|
5
5
|
prerelease:
|
|
6
6
|
segments:
|
|
7
7
|
- 1
|
|
8
|
+
- 1
|
|
8
9
|
- 0
|
|
9
|
-
|
|
10
|
-
version: 1.0.0
|
|
10
|
+
version: 1.1.0
|
|
11
11
|
platform: ruby
|
|
12
12
|
authors:
|
|
13
13
|
- David Majda
|
|
@@ -15,8 +15,7 @@ autorequire:
|
|
|
15
15
|
bindir: bin
|
|
16
16
|
cert_chain: []
|
|
17
17
|
|
|
18
|
-
date: 2012-
|
|
19
|
-
default_executable:
|
|
18
|
+
date: 2012-05-02 00:00:00 Z
|
|
20
19
|
dependencies:
|
|
21
20
|
- !ruby/object:Gem::Dependency
|
|
22
21
|
name: rspec
|
|
@@ -73,7 +72,6 @@ files:
|
|
|
73
72
|
- README.md
|
|
74
73
|
- VERSION
|
|
75
74
|
- lib/abstract_method.rb
|
|
76
|
-
has_rdoc: true
|
|
77
75
|
homepage: https://github.com/openSUSE/abstract_method
|
|
78
76
|
licenses:
|
|
79
77
|
- MIT
|
|
@@ -103,7 +101,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
|
|
|
103
101
|
requirements: []
|
|
104
102
|
|
|
105
103
|
rubyforge_project:
|
|
106
|
-
rubygems_version: 1.
|
|
104
|
+
rubygems_version: 1.8.15
|
|
107
105
|
signing_key:
|
|
108
106
|
specification_version: 3
|
|
109
107
|
summary: Tiny library enabling you to define abstract methods in Ruby classes and modules
|