Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris
 
PerlMonks  

Re^2: Perl 5 Optimizing Compiler, Part 9: RPerl.org & The Low-Magic Perl Commandments

by Will_the_Chill (Pilgrim)
on Nov 18, 2013 at 17:19 UTC ( [id://1063171]=note: print w/replies, xml ) Need Help??


in reply to Re: Perl 5 Optimizing Compiler, Part 9: RPerl.org & The Low-Magic Perl Commandments
in thread Perl 5 Optimizing Compiler, Part 9: RPerl.org & The Low-Magic Perl Commandments

ysth,

Thanks for the info!

I looked at kurila and found that, while it is also a Perl 11 type project like RPerl, our differences outweigh our similarities...

From Kurila Intro POD:

Goals

Experimenting with the Perl language.
RPerl is only experimenting with speed, not new language features.

Removing ugly things.
Yes RPerl does remove some ugly parts of Perl 5.

Adding ugly things.
Heck no, RPerl isn't adding anything to Perl 5 other than speed, much less ugly things!

Changing old design decisions.
RPerl is only against slowness, not necessarily actual design decisions.

Readable, modifiable perl source.
Okay, sure, we all want more readable code, right? Right???

Kurila is not intended to be compatible with Perl 5.
RPerl compiles low-magic Perl 5 code into drop-in Perl-5-compatible replacement functions. Backward compatibility with Perl 5 and XS is important to RPerl.

Interesting stuff!

Perling,
~ Will the Chill
  • Comment on Re^2: Perl 5 Optimizing Compiler, Part 9: RPerl.org & The Low-Magic Perl Commandments

Replies are listed 'Best First'.
Re^3: Perl 5 Optimizing Compiler, Part 9: RPerl.org & The Low-Magic Perl Commandments
by vkon (Curate) on Nov 22, 2013 at 17:47 UTC
    although there are couple of unessential differences that you mentioned, there is one huge common thing between kurila and your rperl - these both have user base approaching to zero....

    read kurila ml archives
    the sooner you understand this the better, in terms of wasted efforts......

    speed is not the goal of perl, for this we have C and inline::c... perl is o(fun) and o(hard things easy) but not for speed.... you're mistargetting the goal, hence the aforementioned epic fail in the future......

      Silly. speed is not the goal of perl, for this we have C and inline::c... the sooner you realize this the sooner you will stop trying to make using Inline::C easier

      Its almost as if you don't want Will the Chill to use Inline::C for speed

        Anonymous Monk is correct, RPerl directly utilizes Inline::C and Inline::CPP to achieve runtime optimization.
        you swapped my sentences and words, and then speculating about this changed content...

        i hereby announce your broken quote of my text as not containing mine thoughts and thus declare your reply invalid...

        dixi

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://1063171]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others drinking their drinks and smoking their pipes about the Monastery: (6)
As of 2024-04-19 10:50 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found