comment on

I'm especially interested to know what a full-on native code compiler can do for you that a JIT can't

Oh I've nothing against JIT. Compilation to native code is compilation to native code (if we ignore all that tedious mucking about with caching and timing of the compiles).

As for benchmarks take a look at Lisp is slow (NOT!) for an example of CMUCL and SBCL (compiled Lisps) beating out C++ in a benchmark.

Please don't take this to mean that I think compilation to native code is necessary, or that interpreted VMs are useless and slow. Premature optimisation and all that. I will quite happily use Perl 6 running on an interpreted Parrot and I'm sure it will do all that I need it to do. The domains that I spend most of my time coding in are not CPU bound.

You just asked "why not just keep the bulk of the code as Parrot" - and speed (for those where it is an actual, rather than an imagined, issue) is one reason.

In reply to Re^4: {Perl6} Macros and native compilation by adrianh
in thread {Perl6} Macros and native compilation by spurperl

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.


Don't ask to ask, just ask
	PerlMonks