Author: lwall
Date: 2009-07-11 18:17:08 +0200 (Sat, 11 Jul 2009)
New Revision: 27507

Modified:
   docs/Perl6/Spec/S03-operators.pod
Log:
[S03] kill Statbuf type, unify with IO role/class somehow


Modified: docs/Perl6/Spec/S03-operators.pod
===================================================================
--- docs/Perl6/Spec/S03-operators.pod   2009-07-11 13:08:14 UTC (rev 27506)
+++ docs/Perl6/Spec/S03-operators.pod   2009-07-11 16:17:08 UTC (rev 27507)
@@ -2222,9 +2222,8 @@
     if $filename.IO.e { say "exists" }
 
 The 1st form actually translates to the latter form, so the object's
-class decides how to dispatch methods.  It just happens that
-C<IO> (filehandles) and C<Statbuf> (stat buffers)
-default to the expected filetest semantics, but C<$regex.i> might
+class decides how to dispatch methods.  It just happens that the
+C<IO> role defaults to the expected filetest semantics, but C<$regex.i> might
 tell you whether the regex is case insensitive, for instance.
 
 Using the pattern form, multiple tests may be combined via junctions:
@@ -2276,13 +2275,10 @@
 when a filename is queried.  The stat buffer will automatically be
 reused if the same object has recently been queried, where "recently"
 is defined as less than a second or so.  If this is a concern, an
-explicit stat() or lstat() may be used to return an explicit stat
-buffer object that will not be subject to timeout, and may be tested
-repeatedly just as a filename or handle can.  A C<Statbuf> object has
-a C<.file> method that can be queried for its filename (if known);
-the C<.io> method returns the handle (if known).  If the C<Statbuf>
-object doesn't know its filename but does know its IO handle, then
-C<.file> attempts to return C<.io.file>.
+explicit stat() or lstat() may be used to return an explicit C<IO>
+object that will not be subject to timeout, and may be tested
+repeatedly just as a filename or handle can.  An C<IO> object has
+a C<.file> method that can be queried for its filename (if known).
 
 (Inadvertent use of the PerlĀ 5 forms will normally result in treatment
 as a negated postdeclared subroutine, which is likely to produce an

Reply via email to