Never attribute to malice that which is adequately explained by human stupidity :)
That said, bravo -- excellent work. I have just one suggestion: Have you perhaps considered using a SQL database (nothing major -- maybe something as simple as SQLite) to manage things? Your script could read one report, and generate the rows as INSERT statements, then read the other report, and fill in the missing data with UPDATE statements.
Perl is great for parsing the incoming data (especially given its heterogeneous nature), but SQL servers shine at the data manipulation you're doing (specifically, the 'inversion' you're performing, plus grouping by date).
Remember: Perl is a very flexible tool, just like a Swiss Army knife. But if I'm turning a lot of screws, I'm not going to reach for my keychain, even if it does have a mini screwdriver; I'm going to use a "real" screwdriver. Sure, my "real" screwdriver doesn't do anything else, but it's way better suited to turning screws.
$"=$,,$_=q>|\p4<6 8p<M/_|<('=> .q>.<4-KI<l|2$<6%s!<qn#F<>;$, .=pack'N*',"@{[unpack'C*',$_] }"for split/</;$_=$,,y[A-Z a-z] {}cd;print lc
In reply to Re: Perl, Authorize.Net, and Broken Kneecaps
by Stevie-O
in thread Perl, Authorize.Net, and Broken Kneecaps
by brian_d_foy
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |