report => [qw/ diag fail print /],
errcont => [1, 'if 1, tests match even if report is fail', 0],
- # fixup for VMS, cygwin, which dont have stderr b4 stdout
+ # fixup for VMS, cygwin, which don't have stderr b4 stdout
rxnoorder => [1, 'if 1, dont req match on -e lines, and -banner',0],
strip => [1, 'if 1, catch errs and remove from renderings',0],
stripv => 'if strip&&1, be verbose about it',
=head2 match criteria
The selected golden-sample is massaged to eliminate various match
-irrelevancies. This is done so that the tests dont fail just because
+irrelevancies. This is done so that the tests don't fail just because
you added a line to the top of the test file. (Recall that the
renderings contain the program's line numbers). Similar cleanups are
done on "strings", hex-constants, etc.
from outside (as is possible using some software from the net), the iterator
will be out of sync with the symbol table. If you expect this to happen, you
can reset the cache by calling this method. In addition, if you pass a FALSE
-value as the first argument, caching will be disabled. It can be reenabled
+value as the first argument, caching will be disabled. It can be re-enabled
later by calling C<clearcache> again with a TRUE value as the first argument.
It returns TRUE or FALSE to indicate whether caching was previously enabled or
disabled, respectively.
=head2 How does C3 work
-C3 works by always preserving local precendence ordering. This essentially
+C3 works by always preserving local precedence ordering. This essentially
means that no class will appear before any of its subclasses. Take, for
instance, the classic diamond inheritance pattern: