I think this is a really interesting and novel idea, and I can't say that I've heard of it before from anyone else.
I think it also might just work.
Now obviously, as you say, there's only so much you can do.
But I don't see why you couldn't at least stub out the classes and methods you see mentioned, and get at least the package, strict, $VERSION, sub new, sub whateveryousee, and so on in place, based soley on what you see in the tests.
You wouldn't get a lot, but you might just get enough to make it interesting and worth while.
I say go for it.
Start with
PPI for the parsing, and then build up a simple model of the classes based on what you see.
Then genenerate the basics for a class and write the files to an appropriately named file, in a position relative to the test file based on normal dist structure.
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.