BrowserUK wrote
"It's deliberately unrunnable, as you don't have the code for f1() or f2() or any sample data. Does that make it too hard?"
Yes. I'd like to hack on this, but without the functions and sample data, my brain swims.
Dragonchild and hv came up with good ideas, but for those of us with less experience, having dummy f1/2 and some sample data would make it a lot easier to see if our ideas were legitimate.
I think you could have coded some dummyup up with a lot less effort than it would take to do unit tests, as dws suggested
Just my 2c!
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
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:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.