Stylistic commentary:
* Re-format everything with an 80 character line. It makes everyone's life miserable if they have to keep scrolling back and forth to read the end the text. In particular, don't be so stingy with the '#' characters. Multiline comments are simply ducky.
* DO you expect the script to "kill your system"? If so, fix the bug. If not, think about *not* including that line. It makes me think more than twice about using your code.
* You might try commenting the regexes you use to identify the comic to be pulled. Either with the 'x' option inline with the regex, or as comment block before each one. This is provides the next person who updates the code a leg up on what to expect from the regex, and it gives you a cross check on whether the regex actually is doing what you just said it does.
* You might want to consider adding a POD stanza to provide external documentation. Give the potential User a paragraph or so description of the Code and What It Does, and they don't have to wade through the code. It's the same principal as a car-seller handing out printed specifications; it keeps the potential buyer from getting down on their knees to look at the under-carriage.
Good luck on the interview.
OGB
In reply to Re: Script Review...
by Old_Gray_Bear
in thread Script Review...
by draxil42
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |