comment on

1. What is your personal interest in a Perl 5 optimizing compiler?

This is something I could probably use at work, where I mostly optimize perl code.

I'm also the author of the perlito compiler. I'm investigating the efficient implementation/emulation of perl semantics on alternative backends. I'm also interested in the parser itself.

2. What part of the project do you feel qualified to work on?

Maybe some parsing, code generation, and optimizations.

3. What XS code have you written?

Almost none

4. What is your level of familiarity with Perl internals?

Almost none

5. Are you more interested in being sponsored to work hard on this project, or just volunteering some of your spare time?

I don't know yet, but the project looks really interesting.

6. Are you in a position to provide some initial pro bono coding effort?

Sure.

In reply to Re: Perl 5 Optimizing Compiler, Part 5: A Vague Outline Emerges by fglock
in thread Perl 5 Optimizing Compiler, Part 5: A Vague Outline Emerges by Will_the_Chill

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.


go ahead... be a heretic
	PerlMonks