Just a quick note that, despite what many have appeared to assume, this may not be a question about the "grep" program as the noder refers to it as "the GREP function". It may simply be that the noder doesn't understand that Perl's grep works on a list of scalars (not on filenames) and requires either braces or a comma (or that was left out when the example was retyped).
jjdeterick should definitely take more care in crafting future questions (cutting and pasting the exact code involved and exactly what output and/or error is generated).
-
tye
(but my friends call me "Tye")
| [reply] |
This isn't a perl question, but this will work:
grep /\[1\]/ filename | [reply] [d/l] |
It will almost
work, but you need a comma...
grep /\[1\]/, filename;
Update voted down? Why? ok, it should probably be @filename, but I just copied it, you do need the comma.
- Ant | [reply] [d/l] |
Probably the downvote because, as indicated (albeit somewhat indirectly), the response concerns unix grep(1), not perl grep, so the comma is not needed. Were it to be in perl, and had the file been read into an array using @file = <>, then grep /\[l\]/, @file would be correct, but from the command line, it ain't.
However, the original response is also wrong: since we're on the command line, the slashes are read as part of the regular expression, not as a pattern delimiter, so what you actually want is either
#!/usr/bin/perl
open FH, "filename" or die "couldn't open file.\n";
@filename = <>;
print grep /\[l\]/,@filename;
or (note single quotes)
% grep '\[l\]' filename
You will note which of them is simpler.
If God had meant us to fly, he would *never* have give us the railroads.
--Michael Flanders | [reply] [d/l] [select] |