From: Rob Kinyon Date: Mon, 27 Feb 2006 14:31:11 +0000 (+0000) Subject: Spelling errors X-Git-Tag: 0_20~10 X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=bf5e889b73ffa24f7c759eac8ef9c671d5b88da7;p=gitmo%2FClass-MOP.git Spelling errors --- diff --git a/lib/Class/MOP/SafeMixin.pm b/lib/Class/MOP/SafeMixin.pm index dd1f186..ff9dc9c 100644 --- a/lib/Class/MOP/SafeMixin.pm +++ b/lib/Class/MOP/SafeMixin.pm @@ -38,7 +38,7 @@ if you so desire. In order to mix classes together, they must inherit from a common superclass. This assures at least some level of similarity between -the classes being mixed together, which should results in a more +the classes being mixed together, which should result in a more stable end product. The only exception to this rule is if the class being mixed in has @@ -90,7 +90,7 @@ solution. In CLOS, I, I and I methods provide a high degree of flexibility for adding behavior to methods, but do not address any concerns regarding classes since in CLOS, classes and methods are -seperate components of the system. +separate components of the system. In Scala, mixins are restricted by their ancestral relationships, which results in a need to have seperate "traits" to get around this restriction. @@ -108,7 +108,7 @@ fact, this feature (IMO) promotes good useage of roles by keeping them both small and simple. But, the same behaviors cannot be applied to class mixins without hitting these barriers all too quickly. -The same too can be said of the original Triats system, with it's +The same too can be said of the original Traits system, with its features for aliasing and exclusion of methods. So after close study of these systems, and in some cases actually @@ -129,4 +129,4 @@ L This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. -=cut \ No newline at end of file +=cut