Uh, I don't understand what you are asking about PPI? But I wish I published earlier so you asked it a few weeks ago. :-) It is like this: A routine trawling some Perl code after
use statements aren't hard to do with PPI, almost a oneliner. PPI works well for me. As it is, it will need to be two phases (first to find declarations). I will put up changes the coming weekend, I hope.
This transpiler is in Perl, so it will be slower to compile than Perl (edit: for instance, see the deep dive into use:d files). In the end, it will probably be generation of a compiled file, with runtime etc. (Edit: I also saw tries with compiled bytecode, now I understand why it never became a thing.)
Edit: I am trying to solve BEGIN now, that is trickier than sub prototypes. But totally doable in CL. The problem now, is that my attempt at a demonstration Perl transpiler to get something to compile to other languages is getting a too complex output.
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.