rule
keyword, which has a usage quite similar to subroutine definitions. Anonymous rules can be introduced with the regex
(or rx
) keyword, or simply be used inline as regexes were in Perl 5 via the m
(matching) or s
(substitution) operators.
History
In ''Apocalypse 5'', a document outlining the preliminary design decisions for Raku pattern matching, Larry Wall enumerated 20 problems with the "current regex culture". Among these were that Perl's regexes were "too compact and 'cute'", had "too much reliance on too few metacharacters", "little support for named captures", "little support for grammars", and "poor integration with 'real' language". Between late 2004 and mid-2005, a compiler for Raku style rules was developed for theChanges from Perl 5
There are only six unchanged features from Perl 5's regexes: * Literals: word characters (letters, numbers and(...)
* Alternatives: ,
* Backslash escape: \
* Repetition quantifiers: *
, +
, and ?
, but not
* Minimal matching suffix: *?
, +?
, ??
A few of the most powerful additions include:
* The ability to reference rules using
to build up entire grammars.
* A handful of commit operators that allow the programmer to control ../code>, which are the same as Perl 5's: (?:...)
* Simplified code assertions: >
* Allows for whitespace to be included without being matched, allowing for multiline regexes. Use \
or ' '
to express whitespace.
* Extended regex formatting (Perl 5's /x
) is now the default.
Implicit changes
Some of the features of Perl 5 regular expressions are more powerful in Raku because of their ability to encapsulate the expanded features of Raku rules. For example, in Perl 5, there were positive and negative lookahead operators (?=...)
and (?!...)
. In Raku these same features exist, but are called
and
.
However, because before
can encapsulate arbitrary rules, it can be used to express lookahead as a syntactic predicate A syntactic predicate specifies the syntactic validity of applying a production in a formal grammar and is analogous to a semantic predicate that specifies the semantic validity of applying a production. It is a simple and effective means of dram ...
for a grammar. For example, the following parsing expression grammar
In computer science, a parsing expression grammar (PEG) is a type of analytic formal grammar, i.e. it describes a formal language in terms of a set of rules for recognizing strings in the language. The formalism was introduced by Bryan Ford in 20 ...
describes the classic non-context-free language :
S ← &(A !b) a+ B
A ← a A? b
B ← b B? c
In Raku rules that would be:
rule S
rule A
rule B
Of course, given the ability to mix rules and regular code, that can be simplified even further:
rule S
However, this makes use of assertions, which is a subtly different concept in Raku rules, but more substantially different in parsing theory, making this a semantic rather than syntactic predicate. The most important difference in practice is performance. There is no way for the rule engine to know what conditions the assertion may match, so no optimization of this process can be made.
Integration with Perl
In many languages, regular expressions are entered as strings, which are then passed to library routines that parse and compile them into an internal state. In Perl 5, regular expressions shared some of the lexical analysis
Lexical tokenization is conversion of a text into (semantically or syntactically) meaningful ''lexical tokens'' belonging to categories defined by a "lexer" program. In case of a natural language, those categories include nouns, verbs, adjectives ...
with Perl's scanner. This simplified many aspects of regular expression usage, though it added a great deal of complexity to the scanner. In Raku, rules are part of the grammar of the language. No separate parser exists for rules, as it did in Perl 5. This means that code, embedded in rules, is parsed at the same time as the rule itself and its surrounding code. For example, it is possible to nest rules and code without re-invoking the parser:
rule ab
The above is a single block of Raku code that contains an outer rule definition, an inner block of assertion code, and inside of that a regex that contains one more level of assertion.
Implementation
Keywords
There are several keywords used in conjunction with Raku rules:
;regex: A named or anonymous regex that ignores whitespace within the regex by default.
;token: A named or anonymous regex that implies the :ratchet
modifier.
;rule: A named or anonymous regex that implies the :ratchet
and :sigspace
modifiers.
;rx: An anonymous regex that takes arbitrary delimiters such as //
where regex only takes braces.
;m: An operator form of anonymous regex that performs matches with arbitrary delimiters.
;mm: Shorthand for m with the :sigspace
modifier.
;s: An operator form of anonymous regex that performs substitution with arbitrary delimiters.
;ss: Shorthand for s with the :sigspace
modifier.
;/.../
: Simply placing a regex between slashes is shorthand for rx/.../
.
Here is an example of typical use:
token word
rule phrase
if $string ~~ / \n /
Modifiers
Modifiers may be placed after any of the regex keywords, and before the delimiter. If a regex is named, the modifier comes after the name. Modifiers control the way regexes are parsed and how they behave. They are always introduced with a leading :
character.
Some of the more important modifiers include:
* :i
or :ignorecase
– Perform matching without respect to case.
* :m
or :ignoremark
– Perform matching without respect to combining characters.
* :g
or :global
– Perform the match more than once on a given target string.
* :s
or :sigspace
– Replace whitespace in the regex with a whitespace-matching rule, rather than simply ignoring it.
* :Perl5
– Treat the regex as a Perl 5 regular expression.
* :ratchet
– Never perform backtracking in the rule.
For example:
regex addition
Grammars
A grammar may be defined using the grammar
operator. A grammar is essentially just a namespace
In computing, a namespace is a set of signs (''names'') that are used to identify and refer to objects of various kinds. A namespace ensures that all of a given set of objects have unique names so that they can be easily identified.
Namespaces ...
for rules:
grammar Str::SprintfFormat
This is the grammar used to define Perl's sprintf
string formatting notation.
Outside of this namespace, you could use these rules like so:
if / /
A rule used in this way is actually identical to the invocation of a subroutine with the extra semantics and side-effects of pattern matching (e.g., rule invocations can be backtracked).
Examples
Here are some example rules in Raku:
rx
rx
That last is identical to:
rx
References
External links
Raku Grammars
- The reference manual page for grammars.
Grammar tutorial
- A tutorial for grammars in Raku
- The standards document covering Perl 6 regexes and rules.
Perl 6 Regex Introduction
- Gentle introduction to Perl 6 regexes.
{{Perl
Raku (programming language)
Regular expressions