Author: larry
Date: Sat Feb 3 09:32:03 2007
New Revision: 13569
Modified:
doc/trunk/design/syn/S03.pod
doc/trunk/design/syn/S12.pod
Log:
s:g/TEST/STATUS/ at suggestion of Smylers++.
Modified: doc/trunk/design/syn/S03.pod
==============================================================================
--- doc/trunk/design/syn/S03.pod (original)
+++ doc/trunk/design/syn/S03.pod Sat Feb 3 09:32:03 2007
@@ -12,9 +12,9 @@
Maintainer: Larry Wall <[EMAIL PROTECTED]>
Date: 8 Mar 2004
- Last Modified: 2 Feb 2007
+ Last Modified: 3 Feb 2007
Number: 3
- Version: 96
+ Version: 97
=head1 Overview
@@ -1416,10 +1416,10 @@
Both of these forms actually translate to
- if $filename.TEST(:e) { say "exists" }
+ if $filename.STATUS(:e) { say "exists" }
which is a generic mechanism that dispatches to the object's
-class to find the definition of C<TEST>. (It just happens that C<Str>
+class to find the definition of C<STATUS>. (It just happens that C<Str>
(filenames) and C<IO> (filehandles) default to the expected filetest
semantics, but C<$regex.:i> might tell you whether the regex is case
insensitive, for instance.)
@@ -2153,7 +2153,7 @@
Any Num numeric equality +$_ == X
Any Str string equality ~$_ eq X
- Any Pair test object .TEST(X) (Str,IO do filetest)
+ Any Pair test object .STATUS(X) (Str,IO do filetest)
Set Set identical sets $_ === X
Hash Set hash keys same set $_.keys === X
Modified: doc/trunk/design/syn/S12.pod
==============================================================================
--- doc/trunk/design/syn/S12.pod (original)
+++ doc/trunk/design/syn/S12.pod Sat Feb 3 09:32:03 2007
@@ -12,9 +12,9 @@
Maintainer: Larry Wall <[EMAIL PROTECTED]>
Date: 27 Oct 2004
- Last Modified: 2 Feb 2007
+ Last Modified: 3 Feb 2007
Number: 12
- Version: 37
+ Version: 38
=head1 Overview
@@ -617,18 +617,18 @@
it actually calls
- $filehandle.TEST(:e)
- $filehandle.TEST(:!x)
+ $filehandle.STATUS(:e)
+ $filehandle.STATUS(:!x)
which is expected to return a value that can be used as a boolean.
While this is primarily intended for use by file tests, other classes
-may define a C<TEST> method to provide a similar mechanism for interrogating
+may define a C<STATUS> method to provide a similar mechanism for interrogating
lightweight properties without having to define methods for all of them.
Note, though, that I<all> such queries are answered by the first located
-C<TEST> method--they are not inherited independently. The C<TEST> method
+C<STATUS> method--they are not inherited independently. The C<STATUS> method
must explicitly pass the query on to other classes in such cases. Likewise,
-if conflicting C<TEST> methods are composed from two different roles, they
+if conflicting C<STATUS> methods are composed from two different roles, they
must be disambiguated as any other conflicting method would be.
Depending on the class, the pairs in question may have arguments.
