Beefy Boxes and Bandwidth Generously Provided by pair Networks
Pathologically Eclectic Rubbish Lister
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??

<keanu>Whoa.</keanu>

Thanks for the more complete writeup of the new regex syntax and semantics. I found it difficult to get a "big picture" idea of how things are expected to work from the Apocalypse, even though that made for some excellent reading. This should keep me satisfied until Exegesis 5 comes out.

I'm going to be very interested to find out how well these grammar-based regular expressions play with Perl 6's increased focus on functional and logical programming (or at least my perception of increased focus). In my admittedly limited experience, thinking in "functional" terms, in "logical" terms, and in "grammar" terms require similar mindsets and methods of reasoning, and I hope that the Perl 6 developers can unify (heh) these facets of the language.

Update: For instance, there are a few hints on dev.perl.org about the Perl 6 parser being retargetable, mungeable, and tied in with the regex engine. With luck, this'll make it easier to treat code as data, which seems to have worked out fairly well for Lisp. (And I'd love to see it in Perl, despite the fact that dealing with Perl code is a much hairier task than dealing with a bunch of (possibly nested (like this)) lists.)

--
The hell with paco, vote for Erudil!
:wq


In reply to Re: Parsing with Perl 6 by FoxtrotUniform
in thread Parsing with Perl 6 by jryan

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



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others examining the Monastery: (8)
As of 2024-03-28 09:16 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found