Hauke that's awesome!!!
I personally have a (too) long running project to exploit the semantic similarities for this goal and already put a lot of theoretical work into it.
JS is for 98% a simplified Perl, and patching B::Deparse to emit native JS should be possible.
But I was confronted with some problems:
- How to translate RegExes, since JS only supports the Perl4 (sub) standard °
- How to handle eval , since compiling the op-tree still needs a Perl parser.
- How to cover the remaining 2 %
- (update) How to cover XS code
Your approach could at least solve the eval bottleneck, my approach could probably lead to faster code and less footprint.
If you're interested I'd love to contribute, even meeting in Berlin for discussion.
°) not sure how you solve this, does asm.js also cover the regex engine? My idea was to use re qw/debug/ to emit an "regex-optree" and translate this.
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.