"1) does size matter?"
The size that matters, is the memory usage and cpu usage of the running process ID. The code size dosn't really matter, and as you keep working on your project, you will probably see where you can put redundant code into subroutines.
In a program that scans alot of files, I would be concerned with "speed". Not to disparage File::Scan, but it is awfully slow compared to a c program like clamav
Personally I would make a Tk frontend for running clamav, through backticks, or IPC::Open3
Looks nice though. :-)
I'm not really a human, but I play one on earth.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||