Re^3: Using grep and glob to find directories containing file

I just want to check that there is no need to explicitly check "if the list has at least one element" since presumably evaluating the list (by grep) will determine if it is empty or not.

Right, no need for an explicit check. Arrays in scalar context evaluate to the number of elements, so only empty arrays are false in boolean context.

The stateful carry over part seems to be weird if not buggy.

Well,

glob</b> needs to carry state for this useful idiom to work:

<code>
while (my $file = glob '*.txt') {
    # do something with $file
}
</code>

<p>Which is more friendly to memory than using a list and iterating th
+at.</p>

<p>But one could argue that <c>glob
[download]

should discard its internal state when called with a different argument.

Perl 6 - the future is here, just unevenly distributed

Comment on Re^3: Using grep and glob to find directories containing file Download Code

Replies are listed 'Best First'.
Re^4: Using grep and glob to find directories containing file by Anonymous Monk on Feb 03, 2013 at 16:47 UTC
Thanks for the help and explanation!!! This behavior is certainly not obvious and it is not (clearly) documented either under 'perldoc -f glob' or at perldoc.perl.org. The line saying "In scalar context, glob iterates through such filename expansions, returning undef when the list is exhausted" does not make it clear (at least to me) that such a state persists across calls to glob with a new argument! In fact, I can imagine all types of unintended errors when glob has been called in a scalar context in one place and then many lines later is called again in a different context and the programmer would have no idea that the state persists. But then again I am not a Perl monk so these things are never obvious to me :)	[reply]
Re^4: Using grep and glob to find directories containing file by Anonymous Monk on Feb 03, 2013 at 17:21 UTC
I still think something is wrong... If I do something like: `mkdir dir1 dir2 touch dir1/f{1,2}` [download] and then run: `foreach (1,2,3,4) { print "dir1\n" if glob("dir1/f"); print "dir2\n" if glob("dir2/f"); }` [download] I get 'dir1' printed 3 times (NOT 4). But if I unwind the loop: `print "dir1\n" if glob("dir1/f"); print "dir2\n" if glob("dir2/f"); print "dir1\n" if glob("dir1/f"); print "dir2\n" if glob("dir2/f"); print "dir1\n" if glob("dir1/f"); print "dir2\n" if glob("dir2/f"); print "dir1\n" if glob("dir1/f"); print "dir2\n" if glob("dir2/f");` [download] Then I get 'dir1' printed 4 times!!! In other words, I can understand why 'glob' is stateful when it is the loop iterator. But it makes no sense (to me) (and seems wrong) for it to be stateful when it is not the iterator. Because then unwinding a loop give a different answer.	[reply] [d/l] [select]
Re^5: Using grep and glob to find directories containing file by 7stud (Deacon) on Feb 03, 2013 at 18:03 UTC
`foreach (1,2,3,4) { print "dir1\n" if glob("dir1/f"); print "dir2\n" if glob("dir2/f"); }` [download] I get 'dir1' printed 3 times I would think your code would print 'dir1' twice. In your second code example, there is no advancing iterator because you can double the number of print statements and you will get double the output. Your first example doesn't tell the whole story. Look at this output: `use strict; use warnings; use 5.012; for my $i (1..10) { print "$i: "; if (my $x = glob "dir1/f") { print "\t$x"; } if (my $y = glob "dir2/f") { print "\t$y"; } print "\n"; } --output:-- 1: dir1/f1 2: dir1/f2 3: 4: dir1/f1 5: dir1/f2 6: 7: dir1/f1 8: dir1/f2 9: 10: dir1/f1` [download] So it appears that inside a loop, once the iterator is exhausted, the next call to glob() returns undef, then the next call to glob() creates a new iterator(or resets the old iterator) and returns the first matching filename again. You can run a similar test on your second example: `use strict; use warnings; use 5.012; if (my $x = glob "dir1/f") { say $x; } if (my $x = glob "dir1/f") { say $x; } if (my $x = glob "dir1/f") { say $x; } if (my $x = glob "dir1/f") { say $x; } if (my $x = glob"dir1/f*") { say $x; } --output:-- dir1/f1 dir1/f1 dir1/f1 dir1/f1 dir1/f1` [download] No loop, no call to the iterator's next() method. So as is often the case, perl examines the context of the statement to determine its return value.	[reply] [d/l] [select]


laziness, impatience, and hubris
	PerlMonks