http://www.perlmonks.org?node_id=1055386


in reply to Re^2: Perl 5 Optimizing Compiler, Part 8: The Book Of RPerl
in thread Perl 5 Optimizing Compiler, Part 8: The Book Of RPerl

I followed the links...and what I found was harder to understand than the original article. And much less entertaining!

If I wanted to get involved, can point me to where I need to go to figure out what it is I'm seeing there? My degree is in engineering (and 30 years old) so I took the assembly language course, not the compiler writing course.

  • Comment on Re^3: Perl 5 Optimizing Compiler, Part 8: The Book Of RPerl

Replies are listed 'Best First'.
Re^4: Perl 5 Optimizing Compiler, Part 8: The Book Of RPerl
by Will_the_Chill (Pilgrim) on Sep 24, 2013 at 05:55 UTC
    GotToBTru: In what ways are you wanting to become involved? As a programmer? As a tester? As a financial supporter? :)
      Programming is what I do; testing is probably more in my immediate reach.
        We're tracking the RPerl project using Trello, there's a basic check-list on a card named "Test Suite" on this board:

        https://trello.com/b/hQCPeg1d/austin-pm-rperl-development

        The in-process test is 05_type_hash.t, which is almost done and is modeled after the working 04_type_array.t. You can see the test file at Github here:

        https://github.com/wbraswell/rperl/blob/master/t/05_type_hash.t

        After the hash type test is done, then comes the OO inheritance test, the RPerl system functionality for which is already in place, and the basic testing code for which is already largely written in different places around the RPerl codebase.

        After the OO inheritance test comes the hand-compiled sorting test, and that's where my RPerl system functionality ends. I'm in the process of choosing a Perl 5 parser now, then comes the automated compiling process.

        Wanna help with some test writing? :)