What meanings do we want to convey?
Regexp are now more like functions, their field of use
has enlarged to the parsing of whole language defined by grammars. And parsing grammar
is
the selling point. What can do more can certainly do less.
I would call them grammexen to get the
point thru: "you can parse using grammexen, you can't using
plain old regexen". It makes clear that perl6 is not only
for assembling or lexing strings but that it can handle
complex languages. grammex ends like regex, so it is a reminder
that it is a related concept.
I want to spell it loud and clear. I don't want to hide the
clue about grammar in an acronym because most acronyms are
anacronyms.
--
stefp -- check out TeXmacs
wiki
-
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.
|
