Re: File test operators as Pairs

2007-04-13 Thread brian d foy
In article <[EMAIL PROTECTED]>, Luke Palmer <[EMAIL PROTECTED]> wrote: > However, now we have stat($file).size. That's sorta fine with me. That makes it even easier to explain to newbies, although I'd need method names for the other tests. However, junctive tests are a mighty attractive featur

Re: File test operators as Pairs

2007-04-13 Thread Brandon S. Allbery KF8NH
On Apr 13, 2007, at 20:09 , Jonathan Lang wrote: What does pair notation buy us that quoted-postfix notation doesn't already cover? I don't think it does. What it does buy is that the *unquoted* notation works: the definition of Perl6's grammar turns out to lead to `-f' and `- f' parsin

Re: File test operators as Pairs

2007-04-13 Thread Jonathan Lang
Luke Palmer wrote: These things are methods, and I'm not sure why we've crammed them into smart match. Things like :M have nothing to do with matching. What would it mean if smart match returned false? "This file has not been modified ever"? :e has a bit more merit for a smart match, but the op

Re: File test operators as Pairs

2007-04-13 Thread Luke Palmer
On 4/13/07, brian d foy <[EMAIL PROTECTED]> wrote: Which then makes me think I'd want to do something a bit wacky to see if the modtime is greater than 5: "doc" ~~ M => any( 5 ..* ); Or even "doc" ~~ M => (5..*). Then again, ("doc" ~~ :M) ~~ 5..* does the same thing, without having to hav

File test operators as Pairs

2007-04-13 Thread brian d foy
So far (eep!), the documentation talks about file test operators as working with pairs, which will be a weird thing to explain, I guess. I'm wondering if this matters to the mere user at all, and if we should even talk about them in terms of "pairs". I don't want a different set of terms in the doc