Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • Your specification was very interesting reading. I'll be interested to see what comes of this. However, I do have some problems with what you put together. To quote from the specification:

    However, [Perl 6] also breaks a lot of compatibility and so will be hard to port existing Perl 5 code to. Perl 6 may eventually be a wonderful language. ``But it's not going to be Perl''.

    It seems to me that you are laboring under a misapprehension that many Perl programmers seem to face. You have addressed two issu

    • First of all, the "But, it's not going to be Perl" sentence was meant as a reference to a similar comment made on Fortran 90. I seem to have misplaced the place where I've seen this quote. Anyone to the rescue?

      Now regarding the difference between Rindolf and Perl 6: I'm trying to put stuff in Rindolf, without bloating the language too much, as opposed to Perl 6 which, IMO, seems like the LCM of all computer languages possible.

      What is not in Rindolf is equally important as what is in there.

      The o

      • Two major problems I have with this reply.

        1) Rindolf is based on Perl 5 which is very complicated with everything in it. You complain about being too complicated but that is what you are basing your core around.

        2) Perl 6 on the other hand is taking the opposite approach and making the core language very tiny. It achieves the same as Perl 5 and more, but by doing it all in separate libraries. This is key to Perl 6.
        • Therefore, would it not make more sense to derive Rindolf from Perl 6 (when it becomes available) than to try and retrofit features onto the scary Perl 5 code base? 8)
          • One should distinguish between the Perl 5 language and the perl 5.6.1 codebase. The Rindolf SPEC does not talk about how to internals of the interpreter will look like.

            Rindolf hackers may eventually use Parrot as our back-end. Or the original perl 5 one. But then, I heard good things about the Ruby codebase, so who knows. ;-)

            From what I know, the intention of the perl 5 hackers is to eventually implement it above Parrot, as Parrot is a generic VM which should be suitable for many high-level language