![\"Until](\"http:\/\/soliloquyforthefallen.net\/images\/xkcd\/regular_expressions.png\" "\\"Stand")
<\/a>Stand Back!<\/p><\/div>\n
Yes indeed.<\/p>\n
use warnings; use strict;\nmy @file_contents;\n\nopen FILE, \"text.txt\" or die \"$!\"; #open with write rights\n@file_contents = <FILE>;\nclose FILE;\nforeach my $text (@file_contents){\n chomp $text;\n if ($text =~ m\/^Strip for \/){\n print $text;\n } else {\n print \"No goodness here (Text:$text) n\"\n }\n}\n<\/pre>\nPretty much what this snippet does is takes and loads the contents of the file into an array, with each line being an item in the array.\u00a0 It then stores one value of the array, chomps the newline character off of the end, and check if it starts with “Strip for”, case sensitively via a regular expression.\u00a0 If the value starts as wanted, then I’m good and it prints that line from the file.\u00a0 If\u00a0 the line does not start with “Strip for”, then it prints “No Goodness here” and what the line actually was.<\/p>\n
This can then be turned into a subroutine to use with perl.<\/p>\n
use warnings; use strict;\nmy @file_contents;\n\nopen FILE, \"text.txt\" or die \"$!\"; #open with write rights\n@file_contents = <FILE>;\nclose FILE;\n\n®_ex(@file_contents);\n\nsub reg_ex{\n foreach my $text (@file_contents){\n chomp $text;\n if ($text =~ m\/^Strip for \/){\n print $text;\n } else {\n print \"No goodness here (Text:$text) n\"\n }\n }\n}\n<\/pre>\nNow, no matter how many different types of data I wanna shove at the array, I just call ®_ex(array of data), and it parse and prints.<\/p>\n
Why is this nice?\u00a0 Let say that I have a more complicated program.\u00a0 Now that I know that section of code works, I can paste that subroutine in, call when needed, and know that it works and is not affecting other parts of my program.\u00a0 Then I can work on debugging the rest of my crappy code.<\/p>\n
Lemme know what you think in the comments, and hopefully I’ll be posting more of this stuff as I go on . . . .<\/p>\n","protected":false},"excerpt":{"rendered":"
What does “Coding Small” mean? Simple. It means code small. A small bit of code is easier to debug then a large program. Take for instance my current Perl coding project. I’m writing a script that will reside on my server and download a comic, and news headlines and then print it out at about… <\/p>\n