# 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 dramatically improving the recognition strength of an LL parser by providing arbitrary lookahead. In their original implementation, syntactic predicates had the form “( α )?” and could only appear on the left edge of a production. The required syntactic condition α could be any valid context-free grammar fragment.

More formally, a syntactic predicate is a form of production intersection, used in parser specifications or in formal grammars. In this sense, the term *predicate* has the meaning of a mathematical indicator function. If *p _{1}* and

*p*are production rules, the language generated by

_{2,}*both*

*p*

_{1}*and*

*p*is their set intersection.

_{2}As typically defined or implemented, syntactic predicates implicitly order the productions so that predicated productions specified earlier have higher precedence than predicated productions specified later within the same decision. This conveys an ability to disambiguate ambiguous productions because the programmer can simply specify which production should match.

Parsing expression grammars (PEGs), invented by Bryan Ford, extend these simple predicates by allowing "not predicates" and permitting a predicate to appear anywhere within a production. Moreover, Ford invented packrat parsing to handle these grammars in linear time by employing memoization, at the cost of heap space.

It is possible to support linear-time parsing of predicates as general as those allowed by PEGs, but reduce the memory cost associated with memoization by avoiding backtracking where some more efficient implementation of lookahead suffices. This approach is implemented by ANTLR version 3, which uses Deterministic finite automata for lookahead; this may require testing a predicate in order to choose between transitions of the DFA (called "pred-LL(*)" parsing).[1]

## Overview

### Terminology

The term *syntactic predicate* was coined by Parr & Quong and differentiates this form of predicate from semantic predicates (also discussed).[2]

Syntactic predicates have been called *multi-step matching*, *parse constraints*, and simply *predicates* in various literature. (See References section below.) This article uses the term *syntactic predicate* throughout for consistency and to distinguish them from semantic predicates.

### Formal closure properties

Bar-Hillel *et al.*[3] show that the intersection of two regular languages is also a regular language, which is to say that the regular languages are closed under intersection.

The intersection of a regular language and a context-free language is also closed, and it has been known at least since Hartmanis[4] that the intersection of two context-free languages is not necessarily a context-free language (and is thus not closed). This can be demonstrated easily using the canonical Type 1 language, :

Let (Type 2) Let (Type 2) Let

Given the strings *abcc*, *aabbc*, and *aaabbbccc*, it is clear that the only string that belongs to both L_{1} **and** L_{2} (that is, the only one that produces a non-empty intersection) is *aaabbbccc*.

### Other considerations

In most formalisms that use syntactic predicates, the syntax of the predicate is noncommutative, which is to say that the operation of predication is ordered. For instance, using the above example, consider the following pseudo-grammar, where *X ::= Y PRED Z* is understood to mean: "*Y* produces *X* if and only if *Y* also satisfies predicate *Z*":

S ::= a X X ::= Y PRED Z Y ::= a+ BNCN Z ::= ANBN c+ BNCN ::= b [BNCN] c ANBN ::= a [ANBN] b

Given the string *aaaabbbccc*, in the case where *Y* must be satisfied *first* (and assuming a greedy implementation), S will generate *aX* and *X* in turn will generate *aaabbbccc*, thereby generating *aaaabbbccc*. In the case where *Z* must be satisfied first, ANBN will fail to generate *aaaabbb*, and thus *aaaabbbccc* is not generated by the grammar. Moreover, if either *Y* or *Z* (or both) specify any action to be taken upon reduction (as would be the case in many parsers), the order that these productions match determines the order in which those side-effects occur. Formalisms that vary over time (such as adaptive grammars) may rely on these side effects.

### Examples of use

- ANTLR

Parr & Quong[5] give this example of a syntactic predicate:

stat: (declaration)? declaration | expression ;

which is intended to satisfy the following informally stated[6] constraints of C++:

- If it looks like a declaration, it is; otherwise
- if it looks like an expression, it is; otherwise
- it is a syntax error.

In the first production of rule stat, the syntactic predicate **(declaration)?** indicates
that declaration is the syntactic context that must be present for the rest of that production to succeed. We can interpret the use of (declaration)? as "I am not sure if
declaration will match; let me try it out and, if it does not match, I shall try the next
alternative." Thus, when encountering a valid declaration, the rule declaration will be
recognized twice—once as syntactic predicate and once during the actual parse to execute semantic actions.

Of note in the above example is the fact that any code triggered by the acceptance of the *declaration* production will only occur if the predicate is satisfied.

#### Canonical examples

The language can be represented in various grammars and formalisms as follows:

- Parsing Expression Grammars

S ← &(A !b) a+ B !c A ← a A? b B ← b B? c

- §-Calculus

Using a *bound* predicate:

S → {A}^{B}

A → X 'c+' X → 'a' [X] 'b' B → 'a+' Y Y → 'b' [Y] 'c'

Using two *free* predicates:

A → <'a+'>_{a}<'b+'>_{b}Ψ(ab)^{X}<'c+'>_{c}Ψ(bc)^{Y}

X → 'a' [X] 'b' Y → 'b' [Y] 'c'

- Conjunctive Grammars

(Note: the following example actually generates , but is included here because it is the example given by the inventor of conjunctive grammars.[7]):

S → AB&DC A → aA | ε B → bBc | ε C → cC | ε D → aDb | ε

- Perl 6 rules

rule S { <before <A> <!before b>> a+ <B> <!before c> } rule A { a <A>? b } rule B { b <B>? c }

## Parsers/formalisms using some form of syntactic predicate

Although by no means an exhaustive list, the following parsers and grammar formalisms employ syntactic predicates:

- ANTLR (Parr & Quong)
- As originally implemented,[2] syntactic predicates sit on the leftmost edge of a production such that the production to the right of the predicate is attempted if and only if the syntactic predicate first accepts the next portion of the input stream. Although ordered, the predicates are checked first, with parsing of a clause continuing if and only if the predicate is satisfied, and semantic actions only occurring in non-predicates.[5]
- Augmented Pattern Matcher (Balmas)
- Balmas refers to syntactic predicates as "multi-step matching" in her paper on APM.[8] As an APM parser parses, it can bind substrings to a variable, and later check this variable against other rules, continuing to parse if and only if that substring is acceptable to further rules.
- Parsing expression grammars (Ford)
- Ford's PEGs have syntactic predicates expressed as the
*and-predicate*and the*not-predicate*.[9] - §-Calculus (Jackson)
- In the §-Calculus, syntactic predicates are originally called simply
*predicates*, but are later divided into*bound*and*free*forms, each with different input properties.[10] - Raku rules
- Raku introduces a generalized tool for describing a grammar called
*rules*, which are an extension of Perl 5's regular expression syntax.[11] Predicates are introduced via a lookahead mechanism called*before*, either with "`<before ...>`

" or "`<!before ...>`

" (that is: "*not*before"). Perl 5 also has such lookahead, but it can only encapsulate Perl 5's more limited regexp features. - ProGrammar (NorKen Technologies)
- ProGrammar's GDL (Grammar Definition Language) makes use of syntactic predicates in a form called
*parse constraints*.[12] - Conjunctive and Boolean Grammars (Okhotin)
- Conjunctive grammars, first introduced by Okhotin,[13] introduce the explicit notion of conjunction-as-predication. Later treatment of conjunctive and boolean grammars[14] is the most thorough treatment of this formalism to date.

## References

- Parr, Terence (2007).
*The Definitive ANTLR Reference: Building Domain-Specific Languages*. The Pragmatic Programmers. p. 328. ISBN 978-3-540-63293-1. - Parr, Terence J.; Quong, Russell (October 1993). "Adding Semantic and Syntactic Predicates to LL(k) parsing: pred-LL(k)". Army High Performance Computing Research Center Preprint No. 93-096. CiteSeerX 10.1.1.26.427. Cite journal requires
`|journal=`

(help) - Bar-Hillel, Y.; Perles, M.; Shamir, E. (1961). "On formal properties of simple phrase structure grammars".
*Zeitschrift für Phonetik, Sprachwissenschaft und Kommunikationsforschung*.**14**(2): 143–172.. - Hartmanis, Juris (1967). "Context-Free Languages and Turing Machine Computations".
*Proceedings of Symposia in Applied Mathematics*. Mathematical Aspects of Computer Science. AMS.**19**: 42–51. doi:10.1090/psapm/019/0235938. ISBN 9780821867280. - Parr, Terence; Quong, Russell (July 1995). "ANTLR: A Predicated-
*LL(k)*Parser Generator" (PDF).*Software—Practice and Experience*.**25**(7): 789–810. doi:10.1002/spe.4380250705. - Stroustrup, Bjarne; Ellis, Margaret A. (1990).
*The Annotated C++ Reference Manual*. Addison-Wesley. - Okhotin, Alexander (2001). "Conjunctive grammars" (PDF).
*Journal of Automata, Languages and Combinatorics*.**6**(4): 519–535. - Balmas, Françoise (20–23 September 1994).
*An Augmented Pattern Matcher as a Tool to Synthesize Conceptual Descriptions of Programs*. Proceedings of the Ninth Knowledged-Based Software Engineering Conference. Monterey, California. pp. 150–157. - Ford, Bryan (September 2002).
*Packrat Parsing: a Practical Linear-Time Algorithm with Backtracking*(Master’s thesis). Massachusetts Institute of Technology. - Jackson, Quinn Tyler (March 2006).
*Adapting to Babel: Adaptivity & Context-Sensitivity in Parsing*. Plymouth, Massachusetts: Ibis Publishing. CiteSeerX 10.1.1.403.8977. - Wall, Larry (2002–2006). "Synopsis 5: Regexes and Rules".
- "Grammar Definition Language". NorKen Technologies.
- Okhotin, Alexander (2000). "On Augmenting the Formalism of Context-Free Grammars with an Intersection Operation".
*Proceedings of the Fourth International Conference "Discrete Models in the Theory of Control Systems"*(in Russian): 106–109. - Okhotin, Alexander (August 2004).
*Boolean Grammars: Expressive Power and Algorithms*(Doctoral thesis). Kingston, Ontario: School of Computing, Queens University.