1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
|
Description: Fix typo in POD
Author: Lucas Kanashiro <kanashiro@debian.org>
Last-Updated: 2017-06-20
Forwarded: https://rt.cpan.org/Ticket/Display.html?id=122148
Bug: https://rt.cpan.org/Ticket/Display.html?id=122148
--- a/lib/Class/EHierarchy.pm
+++ b/lib/Class/EHierarchy.pm
@@ -1801,7 +1801,7 @@ parent object.
This class simplifies the formalization of these relationships, which can have
a couple of benefits. Consider a row object that was retrieved, for example.
-If each of the columns was implmented as a property in the object one could
+If each of the columns was implemented as a property in the object one could
allow in-memory modification of data with a delayed commit. When the
connection goes out of scope you could code your application to flush those
in-memory modifications back to the database prior to garbage collection.
@@ -1831,7 +1831,7 @@ structures, you would be reduced to exec
possibly executing code paths again to account for a few changed properties.
This class explicitly separates assignment of properties from initialization,
-allowing you to execute those code paths only once. OOP implemenations of
+allowing you to execute those code paths only once. OOP implementations of
mathematical constructs, for instance, could significantly alter the values
derived from objects simply by subclassing and overriding some property
values. The original class' initializer will be run once, but using the new
@@ -1849,7 +1849,7 @@ The class hierarchal features necessaril
opaque objects. Objects aren't blessed hashes, they are scalar references
with all properties stored in class data structures.
-The property implementation was made to be flexible to accomodate most needs.
+The property implementation was made to be flexible to accommodate most needs.
A property can be a scalar value, but it also can be an array, hash, or a
number of specific types of references.
@@ -1961,7 +1961,7 @@ object you can place a B<_deconstruct> m
B<_deconstruct> is an optional method which, if present, will be called during
the object's B<DESTROY> phase. It will be called I<after> all children have
-completed thier B<DESTROY> phase. In keeping with the class hierarchal
+completed their B<DESTROY> phase. In keeping with the class hierarchal
features all superclasses will have their B<_deconstruct> methods called after
your subclass' method is called, but prior to finishing the B<DESTROY> phase.
@@ -2168,7 +2168,7 @@ non-existent properties or invalid types
$rv = $obj->exists($prop, $key);
-This method checks for the existance of the specified key in the hash
+This method checks for the existence of the specified key in the hash
property. It returns the return value from the B<exists> function, or
undef on non-existent properties or invalid types.
|
