I mean its often better to attack a problem with tr, split, etc rather than building a regex to solve a problem thats already solved by a pattern based function, even using a glob or some other function.
Of course if there is a module that parses something better - be is Parse::Excel, DBD::CSV or Parse::RecDescent (eeek! grammars!!) then we should use those.
I was just surprised that I wrote a huge and awkward regex to parse lines of IIS logs when they were a space seperated list with a handy dandy c
--
@JAPH = qw(Hacker Perl Another Just);
print reverse @JAPH;
Subversive Regex (Score:1)
-Dom
Re:Subversive Regex (Score:1)
I mean its often better to attack a problem with tr, split, etc rather than building a regex to solve a problem thats already solved by a pattern based function, even using a glob or some other function.
Of course if there is a module that parses something better - be is Parse::Excel, DBD::CSV or Parse::RecDescent (eeek! grammars!!) then we should use those.
I was just surprised that I wrote a huge and awkward regex to parse lines of IIS logs when they were a space seperated list with a handy dandy c
@JAPH = qw(Hacker Perl Another Just);
print reverse @JAPH;