Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl-Sensitive Sunglasses

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
Yes, I'm looking forward to trying it out. I've never used it.

If you decide to have a go this year, start by visiting the IRC channel #perl6 on freenode between about 10am and 10pm GMT (most Perl 6 hackers are based in Europe) and asking questions. The channel has a very friendly and productive vibe -- and folk like Nicholas Clark and Stevan Little have begun to hang out there in recent weeks which is fun too.

I've given an example (which took me approximately 30 seconds to find using google) elsewhere in this thread of a core feature that doesn't yet exist.

Hmm. I don't see it. (I see two posts to this thread using the DrHyde nick, the one that was general and this one which I'm replying to.)

I understand that object introspection and macros are also still not implemented.

Object introspection was implemented early in Rakudo's life (2008?). It's a fairly mature feature at this point. Fwiw here's a search of the #perl6 logs for "introspection".

Carl Mäsak first dreamed of macros in Perl 6 around 2005/2006 iirc, and began fleshing out a design for Rakudo in 2011. He landed an initial implementation of hygienic AST macros (ie Lisp style, not C style) in late 2012.

If I didn't already have a set of excellent tools available, then I might consider using perl 6 even in its current state - just like I did back with early perl 5.

Imo it's about 18 months too early for those whose focus is getting stuff done rather than having fun helping productize Perl 6.

In contrast I think that Perl 6 is attractive to those who want to have fun trying to find things Perl 6 is particularly good at, pushing against its rough edges, and contributing to its improvement.

In reply to Re^6: Perl 6 is going to get a lot faster in 2013 by raiph
in thread Perl 6 is going to get a lot faster in 2013 by raiph

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.
  • Log In?

    What's my password?
    Create A New User
    [hippo]: Too true :)

    How do I use this? | Other CB clients
    Other Users?
    Others studying the Monastery: (8)
    As of 2018-06-22 09:58 GMT
    Find Nodes?
      Voting Booth?
      Should cpanminus be part of the standard Perl release?

      Results (124 votes). Check out past polls.