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.
  • The top five things holding me back from using Rakudo for anything but experimental playing with Perl 6 are (in order of imporatance):

    1. lack of lazy evaluation
    2. s/// is not implemented
    3. it cannot be installed ("removing or moving the build tree will cause the binary to stop working")
    4. I cannot easily tell what parts of the spec are implemented and which are not
    5. The REPL has executes every line in its own scope making lexical variables (and therefore the REPL itself) next to useless.

    I may be wrong abou

    • All of these issues are slated to be resolved by the time Rakudo Star is released. Indeed, I expect that all of them except for #4 will be resolved by the September 2009 compiler release.

      #2 can already be done in current versions of Rakudo, just use .subst() instead of s///. The s/// form should be available when we start using the parser in Rakudo, currently planned for December 2009.


      • That makes me happy. It would be nice if there were an article about what is planned to be (or not be, if that is shorter) in Rakudo Star. Of course, it is entirely possible there is already a road map on a public site that I have not seen yet, and there is still a lot of time until Spring.

        I am not worried about the spec (and therefore the implementations) changing or growing; I am worried about how much of what is currently spec'ed will be implemented by the deadline. A Perl 6 implementation that can't

        • It would be nice if there were an article about what is planned to be (or not be, if that is shorter) in Rakudo Star.

          We worked on this at YAPC::EU in Lisbon, I'm currently in the process of writing it up to be somewhat coherent and understandable. Stay tuned.

          A Perl 6 implementation that can't do what the spec says is Perl 6 doesn't seem to be a real release to me.

          The whole point of Rakudo Star is to say "this isn't all of Perl 6". Anyone that gets Rakudo Star and expects all of Perl 6 to be implemented by then will undoubtedly be disappointed.

          I see it as being promised Perl 5, but having to settle for Perl 4.

          Rakudo Star is all about making a new promise: "The full Perl 6 language isn't done, but here are the parts you can safely start using." If we have to avoid making any sort of usable release until all of "promised Perl 6" is ready, we'll never get there.

          If I understand what I have read about Perl 6, * is whatever, which means it will be the "Rakudo, whatever", release. Not a very inspiring name.

          Actually, an uninspiring name is quite okay with me. I don't want to hype the release, I don't want it to be easy for people to conclude "Perl 6 will be done in April" only to suffer extreme disappointment when Rakudo Star arrives. If the name "Rakudo Star" helps in any way to make people realize "this is not the 1.0 release you're looking for", then it's hitting its intended mark exactly.