comment on

You should be more specific which kind of optimization at compile time you are missing, I doubt there is much potential left.

Perl has dynamic typing which means higher performance is only possible by JIT-ing once the types are (statistically) known (i.e."code paths" are recorded at run-time)

The other way is explicit typing of variables by the author, allowing to optimize crucial sub-routines at compile time.

JS (JIT) resp Typescript (Typing) can do both now.

But as I said, please show us a way to improve ahead of time compilation of vanilla Perl without types.

edit

Furthermore I'm not sure if Perl can even write such optimized machine code without being bundled with a C-compiler.

Theoretically once could use typed variables to create Inline::C blocks. But I'm ignorant about other possibilities here...

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

Wikisyntax for the Monastery}

In reply to Re: Trading compile time for faster runtime? by LanX
in thread Trading compile time for faster runtime? by melez

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.


Keep It Simple, Stupid
	PerlMonks