comment on

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.

Cheers Rolf
_{(addicted to the Perl Programming Language :)

Wikisyntax for the Monastery
FootballPerl is like chess, only without the dice}

°) 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.

In reply to Re: Run Perl 5 in the Browser! by LanX
in thread Run Perl 5 in the Browser! by haukex

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


No such thing as a small change
	PerlMonks