For a few years now, a large part of my job has depended on my writing and maintaining Perl scripts. I thought it would be wise, for my own sake, to note down some of the things I’ve learned along the way. I don’t claim these notes to contain optimal solutions and look forward to any comments they may spark.<\/p>\n
I wasn’t the one to come up with this exact format, and I feel like some of it is extra, however, it has worked and was proliferated throughout many files before I picked them up, so once I have the need to use it for myself, I’ll take the opportunity to figure out what’s really needed. It does show the flexibility of what can be added in the We had multiple projects which were very similar in what needed to be done via the Perl scripts. To keep the code from being hardcoded to a project, we used a Perl module With access to this hash, if I want to apply a label, I can grab the information as long as I know what product I need the information for using something like $Custom::Project::Products{“SourceA_Product”}{label_name}. Or if I’d like to cycle through the subproducts of Top_Product, I can use the array directly by using @{$Custom::Project::Products{“Top_Product”}{subproducts}}<\/p>\n Sometimes it can be useful to store a regex in a variable. In one instance I setup a regex in a variable because it had changed a couple times already, and it was part of a few steps of substitutions, so I wanted to pull out what I could. What I did was create a variable<\/p>\n Then, later, in the substitution phase, I was able to do something like this:<\/p>\n Important here is that the number in the text to be replaced was captured and used in the replacement text.<\/p>\n Instead of Previously, I had always used shift to pop the values passed to subroutines. There is an alternative which looks something like this<\/p>\n Since Perl doesn’t require you to be strict about dictating what will be passed where, this makes a simple way to quickly write out the arguments passed through, though does require attention be paid when making changes. However, I feel it is more readable than using repetitive shifts. There are a few different ways to execute something from within a Perl script. They all return slightly differently, meaning it’s important to choose the right one.<\/p>\n I know there is also an option open(), but I’m not as familiar with it in terms of executing commands, instead of things like opening files. I will direct you to Perl HowTo<\/a> if you wish for more detailed descriptions.<\/p>\n This may not be an issue if you’re on a Unix or Linux machine, but if you’re on a Windows machine and the file you’re creating needs to have the Unix newline format, there’s an one extra step you can take to make it happen.<\/p>\n Sometimes it’s possible to perform tasks in parallel, and Perl has a few options for performing parallel tasks, but I’ve started to prefer threads (& threads::shared).<\/p>\n I did at one point run across a problem due to the size of what was being built by several threads, but I was able to alleviate the problem by increase the stack size by replacing Here 4096 is the page size, and I can’t recall if I ever determined the default stack size, but this size seemed to be sufficient.<\/p>\n Although it’s nice to fully automate tasks, sometimes, there are things you cannot escape requiring the user to do. In one such case, I decided that command line prompting would not be sufficient, so I opted to present the user with a dialog box.<\/p>\n For a few years now, a large part of my job has depended on my writing and maintaining Perl scripts. I thought it would be wise, for my own sake, to note down some of the things I’ve learned along … Continue reading BEGIN<\/code> block as is.<\/p>\nBEGIN\r\n{\r\n\u00a0\u00a0 \u00a0use File::Spec::Functions 'catfile';\r\n\u00a0\u00a0 \u00a0use File::Basename 'dirname';\r\n\u00a0\u00a0 \u00a0push @INC, catfile(dirname($0), '..\/other_location\/Perl_modules');\r\n}<\/pre>\nGeneric Code, Project Specifics in a Hash<\/h1>\n
Custom::Project<\/code>, containing a hash with details about the products and their dependencies. For instance, one layout might be:<\/p>\npackage Custom::Project;\r\n...\r\n %Products = (\r\n SourceA_Product => {\r\n path => \"source_a\",\r\n label_name => \"MYSOURCEA\",\r\n },\r\n SourceB_Product => {\r\n path => \"source_b\",\r\n label_name => \"MYSOURCEB\",\r\n },\r\n Top_Product => {\r\n path => \"top\",\r\n label_name => \"TOP\",\r\n subproducts => [\"SourceA_Product\", \"SourceB_Product\"],\r\n \u00a0},\r\n );<\/pre>\nPrecompile a Regex<\/h2>\n
my $to_be_replaced = qr\/NUMBER_(\\d)_REPLACEABLE\/;<\/pre>\n
$file_contents =~ s\/$to_be_replaced\/New_Name_$1\/g;<\/pre>\n
Name both key and value when iterating over a hash<\/h1>\n
foreach<\/code> and only naming a key, an alternative is to use<\/p>\nwhile ((my $key, my $value) = each %hash) {}<\/pre>\nPassing values to subroutines<\/h1>\n
my ($value1, $value2, $value3) = @_;<\/pre>\n
\nA second point is not really specific to argument passing, but is useful to the cause. Obviously you cannot pass an array to a subroutine directly as the way the arguments are passed is fairly blatantly like an array based on my above note. Passing an array can be critical, though, and it’s not out of the question, it’s simply a matter of how you pass it. Instead of pushing the whole array in by passing it as @my_array<\/code>, you can pass a reference to the array using \\@my_array<\/code>. Once the subroutine receives it, it will need to dereference what it receives, we’ll call it $my_array_ref<\/code> in the subroutine, as such: @{$my_array_ref}<\/code>. Note that this goes for returning information from a subroutine as well; you can return multiple parameters, and they can be references.<\/p>\nExecution Calls<\/h1>\n
system($CMD); # Returns success or failure result\r\n`$CMD`; # Returns output of running command (the characters are backticks and this is effectively the same as qx\/$CMD\/; & qx{$CMD};)\r\nexec($CMD); # Does not return<\/pre>\nSaving a file with Unix newlines<\/h1>\n
my $result = open(FILE, \">\" . $filename) ? 0 : 1;\r\nbinmode FILE;<\/pre>\n
Parallel tasks<\/h1>\n
use threads;\r\nuse threads::shared;\r\n...\r\nmy @threads;\r\nforeach my $folder (@list)\r\n{\r\n my $thr = threads->new(\\&MyFunction, $arg1, $arg2, $arg3);\r\n push(@threads, $thr);\r\n}\r\nforeach (@threads)\r\n{\r\n $result = $_->join;\r\n die \"Failed with result $result\\n\" if ($result);\r\n}\r\nundef @threads;<\/pre>\nuse threads;<\/code> with:<\/p>\nuse threads ('stack_size' => 4096 * 10);<\/pre>\nDialog Boxes<\/h1>\n
use Tk;\r\nuse Tk::DialogBox;\r\n...\r\ndo {\r\n my $mw = MainWindow->new;\r\n $mw->withdraw();\r\n $dialog_response = $mw->messageBox(-title=>\"My Dialog Box Title\",\r\n\t\t -message=>\"Please answer Yes or No to my question here\",\r\n\t\t -type=>\"YesNo\"\r\n\t\t );\r\n} while ($dialog_response ne \"Yes\");<\/pre>\n","protected":false},"excerpt":{"rendered":"