Syntactic predicate

From Wikipedia, the free encyclopedia

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.

Syntactic predicates implicitly order of 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, invented by Bryan Ford, are a powerful formalization and extension to these simple predicates (e.g., PEGs include "not predicates" and allow predicates anywhere within a production). Morever, Bryan invented packrat parsing to handle these grammars in linear time (at the cost of heap space). ANTLR version 3 keeps the same simple predicate structure, but uses rule memoization to also guarantee linear time for predicated parsing.

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 p1 and p2, are production rules, the language generated by both p1 and p2 is their set intersection.

Contents

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

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.

Bar-Hillel et al.[2] 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[3] 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, L = \{ a^n b^n c^n : n \ge 1 \}:

Let L_1 = \{ a^m b^n c^n : m,n \ge 1 \} (Type 2)
Let L_2 = \{ a^n b^n c^m : m,n \ge 1 \} (Type 2)
Let L_3 = L_1 \cap L_2 

Given the strings abcc, aabbc, and aaabbbccc, it is clear that the only string that belongs to both L1 and L2 (that is, the only one that produces a non-empty intersection) is aaabbbccc.

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 satisified 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.

ANTLR

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

stat: (declaration)? declaration 
    | expression 
    ;

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

  1. If it looks like a declaration, it is; otherwise
  2. if it looks like an expression, it is; otherwise
  3. 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 satisified.

The language L = \{a^n b^n c^n | n \ge 1\} 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 Ψ(a b)X <'c+'>c Ψ(b c)Y

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

(Note: the following example actually generates L = \{a^n b^n c^n | n \ge 0\}, but is included here because it is the example given by the inventor of conjunctive grammars.[6]):

S → AB&DC
A → aA | ε
B → bBc | ε
C → cC | ε
D → aDb | ε
Perl 6 rules
rule S {  > a+   }
rule A { a ? b }
rule B { b ? c }


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

ANTLR (Parr & Quong)
As originally implemented,[1] 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 satisified, and semantic actions only occurring in non-predicates.[4]
Augmented Pattern Matcher (Balmas)
Balmas refers to syntactic predicates as "multi-step matching" in her paper on APM.[7] 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.[8]
§-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.[9]
Perl 6 rules
Perl 6 introduces a generalized tool for describing a grammar called rules, which are an extension of Perl 5's regular expression syntax.[10] Predicates are introduced via a lookahead mechanism called before, either with "" or "" (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.[11]
Conjunctive and Boolean Grammars (Okhotin)
Conjunctive grammars, first introduced by Okhotin,[12] introduce the explicit notion of conjunction-as-predication. Later treatment of conjunctive and boolean grammars[13] is the most thorough treatment of this formalism to date.

  1. ^ a b Parr, Terence J.& Quong, Russell, "Adding Semantic and Syntactic Predicates to LL(k) parsing: pred-LL(k)," Army High Performance Computing Research Center Preprint No. 93-096, October 1993.
  2. ^ Bar-Hillel, Y. et al., "On Formal Properties of Simple Phrase Structure Grammars," Zeitschrift für Phonetik, Sprachwissenschaft und Kommunikationsforschung, Vol. 14 No. 2, pp. 143-172, 1961.
  3. ^ Hartmanis, Juris, "Context-Free Languages and Turing Machine Computations," Proceedings of Symposia in Applied Mathematics, Vol. 19, Mathematical Aspects of Computer Science, AMS, pp. 42-51, 1967.
  4. ^ a b Parr, Terence & Quong, Russell, "ANTLR: A Predicated-LL(k) Parser Generator," Software--Practice and Experience, Vol. 25, No. 7, pp. 789-810, July 1995.
  5. ^ Stroustrup, Bjarne & Ellis, Margaret A., The Annotated C++ Reference Manual, Addison-Wesley, 1990.
  6. ^ Okhotin, Alexander, "Conjunctive grammars," Journal of Automata, Languages and Combinatorics, Vol. 6, No. 4, pp. 519-535, 2001
  7. ^ Balmas, Françoise, "An Augmented Pattern Matcher as a Tool to Synthesize Conceptual Descriptions of Programs," Proceedings of the Ninth Knowledged-Based Software Engineering Conference, pp. 150-157, Monterey, California, 20-23 September 1994.
  8. ^ Ford, Bryan, Packrat Parsing: a Practical Linear-Time Algorithm with Backtracking, Master’s thesis, Massachusetts Institute of Technology, September 2002.
  9. ^ Jackson, Quinn Tyler, Adapting to Babel: Adaptivity & Context-Sensitivity in Parsing, Ibis Publishing, Plymouth, Massachusetts, March 2006.
  10. ^ Wall, Larry, "Synopsis 5: Regexes and Rules," 2002-2006.
  11. ^ NorKen Technologies website, "Grammar Definition Language" page.
  12. ^ Okhotin, Alexander, "On Augmenting the Formalism of Context-Free Grammars with an Intersection Operation," (in Russian), Proceedings of the Fourth International Conference "Discrete Models in the Theory of Control Systems," pp. 106-109, 2000.
  13. ^ Okhotin, Alexander, Boolean Grammars: Expressive Power and Algorithms, Doctoral thesis, School of Computing, Queens University, Kingston, Ontario, August 2004.

Advanced Search
Included Web Search Engines


Safe Search

close

Top Matching Results

Occasionally Search.com will highlight specialized results that are based on the context of your query. Examples of specialized results include specific links to news, images, or video.

Top Matching Results may highlight information from other Search.com pages, content from the CNET Network of sites, or third party content. The listings are based purely on relevance. Search.com does not receive payment for listings in this section but our partners that provide this data may get paid for listing these products.

Sponsored Links

This section contains paid listings which have been purchased by companies that want to have their sites appear for specific search terms and related content. These listings are administered, sorted and maintained by a third party and are not endorsed by Search.com.

Search Results

Search.com sends your search query to several search engines at one time and integrates the results into one list which has been sorted by relevance using Search.com's proprietary algorithm. You can customize the list of search engines included in your metasearch from the preferences.

The search engines that are used in your metasearch may allow companies to pay to have their Web sites included within the results. To view the Paid Inclusion policy for a specific search engine, please visit their Web site. Search.com does not accept payment or share revenue with any search engine partner for listings in this section.