DOCSLIB.ORG

A Declarative Extension of Parsing Expression Grammars for Recognizing Most Programming Languages

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
A Declarative Extension of Parsing Expression Grammars for Recognizing Most Programming Languages Journal of Information Processing Vol.24 No.2 256–264 (Mar. 2016) [DOI: 10.2197/ipsjjip.24.256] Regular Paper A Declarative Extension of Parsing Expression Grammars for Recognizing Most Programming Languages Tetsuro Matsumura1,†1 Kimio Kuramitsu1,a) Received: May 18, 2015, Accepted: November 5, 2015 Abstract: Parsing Expression Grammars are a popular foundation for describing syntax. Unfortunately, several syn- tax of programming languages are still hard to recognize with pure PEGs. Notorious cases appears: typedef-defined names in C/C++, indentation-based code layout in Python, and HERE document in many scripting languages. To recognize such PEG-hard syntax, we have addressed a declarative extension to PEGs. The “declarative” extension means no programmed semantic actions, which are traditionally used to realize the extended parsing behavior. Nez is our extended PEG language, including symbol tables and conditional parsing. This paper demonstrates that the use of Nez Extensions can realize many practical programming languages, such as C, C#, Ruby, and Python, which involve PEG-hard syntax. Keywords: parsing expression grammars, semantic actions, context-sensitive syntax, and case studies on program- ming languages invalidate the declarative property of PEGs, thus resulting in re- 1. Introduction duced reusability of grammars. As a result, many developers need Parsing Expression Grammars [5], or PEGs, are a popu- to redevelop grammars for their software engineering tools. lar foundation for describing programming language syntax [6], In this paper, we propose a declarative extension of PEGs for [15]. Indeed, the formalism of PEGs has many desirable prop- recognizing context-sensitive syntax. The “declarative” exten- erties, including deterministic behaviors, unlimited look-aheads, sion means no arbitrary semantic actions that are written in a gen- and integrated lexical analysis known as scanner-less parsing. eral purpose programming language. In our proposal, a variety of Due to these properties, PEGs allow grammar developers to avoid semantic actions are abstracted to two modeled states: the dangling if-else problem and to express the contextual tokens • Symbol Table – a table that manages a list of symbols that and the nested block comment, which are known problems in tra- are differently treaded in a specific context ditional LR(k) and LL(k) grammars. • Parsing Condition – a Boolean flag that dynamically Despite the powerful features of PEGs, several real syntax used switches the parsing behaviors. in popular programming languages is hard to express. This prob- Nez is an extended PEG language that is designed to provide lem comes chiefly from context-sensitive syntax, whose mean- additional operators to handle the above states in parsing contexts ings are changed depending on the parsing context. Typical ex- of PEGs. In this paper, we call Nez extensions to distinguish from amples of such syntax are: pure PEGs operators. • Typedef-defined name in C/C++ [5], [6] Using Nez, we have performed extensive case studies by spec- • HERE document appearing in Perl, Ruby, and other many ifying various popular programming languages. The grammars scripting languages that we have developed for now include C, Java, C#, JavaScript, • Indentation-based code layout appearing in Python and Lua, Ruby, and Python. Since these grammars include many Haskell [1] context-sensitive syntax, we conclude that Nez extensions pro- • Contextual keywords used in C# and other evolving lan- vide improved expressiveness for programming languages in guages [3] practical manners. Technically, a language grammar involving such context- The remainder of this paper proceeds as follows. Section 2 de- sensitive syntax is implemented with semantic actions [8], an em- scribes PEG-hard syntax patterns. Section 3 presents a language bedded code that is hocked to execute the extended action at the design for Nez. Section 4 demonstrates case studies with our parsing time. Since semantic actions are written in a host lan- emphasis on Nez extensions. Section 5 briefly reviews related guage of the generated parser, the use of semantic actions may work. Section 6 concludes the paper. The tools and grammars that are presented in this paper are available online at http://nez- 1 Graduate School of Electronic and Computer Engineering, Yokohama peg.github.io/. National University, Yokohama, Kanagawa 240–8501, Japan †1 Presently with Zuken Inc. a) [email protected] c 2016 Information Processing Society of Japan 256 Journal of Information Processing Vol.24 No.2 256–264 (Mar. 2016) • a type cast of the number 1 to the type T 2. Background and Problem Statement Note that Java avoids this problem by a careful design of lan- 2.1 PEGs guage syntax. The casting (T)-1 is disallowed by restricting that PEGs are a recognition-based foundation for describing syn- the unary + and - is only available for primitive number types. tax, formalized by Ford [5]. While PEGs are relatively new, most 2.2.2 HERE Document (in Ruby, Bash, etc.) of their notations are familiar, coming from EBNF (e.g., produc- The HERE document is a string literal for multiple lines, tions and recursive nonterminals) and regular expressions (kleene widely adopted in scripting languages, such as Bash, Perl, and operators such as ? and *). Figure 1 shows a PEG, which ex- Ruby. While there are many variations, the users are in common presses the basic mathematical notations. allowed to define a delimiting identifier that stands for an end of The interpretation of PEGs significantly differs from CFGs in lines. In the following, the symbol END is an example of the user- that PEG’s choice is ordered. That is, the first subexpression of defined delimiting identifier. a choice is always matched first, and the next subexpression is print <<END attempted only if the first fails. This brings us to deterministic the string parsing behavior, which is regarded as desirable for parsing non- next line natural languages. The ordered choice, on the contrary, disallows END the left recursion, because the deterministic interpretation of the In PEGs, the syntax of a HERE document can be specified with left recursion results in unlimited looping. The PEG example in multi-lines that continue until the nonterminal DELIM is matched Fig. 1 is defined in a form of eliminating left recursions. in the head of a line. However, we cannot assume specific key- The expressiveness of PEGs is almost similar to that of deter- words or possible identifiers to define DELIM, since the user- ministic CFGs (such as LALR and LL family). In general, PEGs defined delimiting identifiers are totally unpredictable. can express all LR grammar languages, which are widely used in 2.2.3 Indentation-based Layout (in Python, Haskell, etc.) a standard parser generator such as Lex/Yacc. In addition, PEG’s Indentation-based code layout is a popular syntax that uses the syntactic predicates (& and !) provide us with the expressiveness depth of indentations for representing the beginning and the end of unlimited look-aheads, suggesting that PEGs are more expres- of a code block. Typically, Python and Haskell are well known sive than CFGs. As a result, PEGs can recognize non context free for such indentation-based code layout, a large number of other languages such as {an bn cn | n > 0}. languages including YAML, F#, and Markdown also use inden- tation. 2.2 Context-Sensitive Syntax PEGs are very powerful, but, in practice, are not able to ex- mapAccumR f = loop press all programming language syntax. This mostly comes from where loop acc (x:xs) = (acc, x : xs) where (acc, x) = f acc x context-sensitive syntax, where the meaning of symbols may vary (acc, xs) = loop acc xs in different contexts. Note that the same limitation commonly ex- loop acc [] = (acc, []) ists in CFG-based grammars. This subsection demonstrates typi- cal examples of context-sensitive syntax. The problem with PEGs is that the user is allowed to use ar- 2.2.1 Typedef-defined Name (in C/C++) bitrary indentation for their code layout. As with in delimiting Typedef-defined name in C/C++ is a typical example of identifiers in the HERE documents, it is hard to prepare all possi- context-sensitive syntax. The identifier is simply supposed as a ble indentations for code layout. sequence of word characters; for example, T is a legal identifier 2.2.4 Contextual Keyword in C# in C/C++. On the other hand, the following typedef statement Popular programming languages are long standing, and then allows the users to declare T as a new type name. evolve to meet the user’s demands. In the language evolution, adding a new keyword is often considered to identify a new syn- typedef unsigned int T; tactical structure. On the other hand, a backward compatibility Once T is a declared type, T is not regarded as an identifier. problem inevitably arises since the added keyword might have In general, the interpretation of an identifier class should be per- already been used as identifiers in legacy code. formed in the phase of semantic analysis, not in syntactic analy- A contextual keyword is used to avoid the compatibility prob- await sis. However, in C/C++, we need to produce a different syntax lem. For example, C#5.0 newly added the keyword, only async tree depending on the contextually varying type of T.Thatis,an available in the qualified method. expression (T)-1 can be parsed differently: async Task<string> GetPageAsync(string path) • a subtract operator of a variable T and the number 1, or { HttpClient c = new HttpClient(); return await c.GetStringAsync(uri + path); } As with in typedef names, the different meaning of await needs to produce different syntax trees in the phase of syntac- tic analysis. It is also hard to specify different syntax analysis Fig. 1 Mathematical Operators in a PEG. c 2016 Information Processing Society of Japan 257 Journal of Information Processing Vol.24 No.2 256–264 (Mar.
Load more

Recommended publications
  • Efficient Recursive Parsing
    Purdue University Purdue e-Pubs Department of Computer Science Technical Reports Department of Computer Science 1976 Efficient Recursive Parsing Christoph M. Hoffmann Purdue University, [email protected] Report Number: 77-215 Hoffmann, Christoph M., "Efficient Recursive Parsing" (1976). Department of Computer Science Technical Reports. Paper 155. https://docs.lib.purdue.edu/cstech/155 This document has been made available through Purdue e-Pubs, a service of the Purdue University Libraries. Please contact [email protected] for additional information. EFFICIENT RECURSIVE PARSING Christoph M. Hoffmann Computer Science Department Purdue University West Lafayette, Indiana 47907 CSD-TR 215 December 1976 Efficient Recursive Parsing Christoph M. Hoffmann Computer Science Department Purdue University- Abstract Algorithms are developed which construct from a given LL(l) grammar a recursive descent parser with as much, recursion resolved by iteration as is possible without introducing auxiliary memory. Unlike other proposed methods in the literature designed to arrive at parsers of this kind, the algorithms do not require extensions of the notational formalism nor alter the grammar in any way. The algorithms constructing the parsers operate in 0(k«s) steps, where s is the size of the grammar, i.e. the sum of the lengths of all productions, and k is a grammar - dependent constant. A speedup of the algorithm is possible which improves the bound to 0(s) for all LL(l) grammars, and constructs smaller parsers with some auxiliary memory in form of parameters
    [Show full text]
  • Advanced Parsing Techniques
    Advanced Parsing Techniques Announcements ● Written Set 1 graded. ● Hard copies available for pickup right now. ● Electronic submissions: feedback returned later today. Where We Are Where We Are Parsing so Far ● We've explored five deterministic parsing algorithms: ● LL(1) ● LR(0) ● SLR(1) ● LALR(1) ● LR(1) ● These algorithms all have their limitations. ● Can we parse arbitrary context-free grammars? Why Parse Arbitrary Grammars? ● They're easier to write. ● Can leave operator precedence and associativity out of the grammar. ● No worries about shift/reduce or FIRST/FOLLOW conflicts. ● If ambiguous, can filter out invalid trees at the end. ● Generate candidate parse trees, then eliminate them when not needed. ● Practical concern for some languages. ● We need to have C and C++ compilers! Questions for Today ● How do you go about parsing ambiguous grammars efficiently? ● How do you produce all possible parse trees? ● What else can we do with a general parser? The Earley Parser Motivation: The Limits of LR ● LR parsers use shift and reduce actions to reduce the input to the start symbol. ● LR parsers cannot deterministically handle shift/reduce or reduce/reduce conflicts. ● However, they can nondeterministically handle these conflicts by guessing which option to choose. ● What if we try all options and see if any of them work? The Earley Parser ● Maintain a collection of Earley items, which are LR(0) items annotated with a start position. ● The item A → α·ω @n means we are working on recognizing A → αω, have seen α, and the start position of the item was the nth token. ● Using techniques similar to LR parsing, try to scan across the input creating these items.
    [Show full text]
  • Verifiable Parse Table Composition for Deterministic Parsing*
    Verifiable Parse Table Composition for Deterministic Parsing? August Schwerdfeger and Eric Van Wyk Department of Computer Science and Engineering University of Minnesota, Minneapolis, MN {schwerdf,evw}@cs.umn.edu Abstract. One obstacle to the implementation of modular extensions to programming languages lies in the problem of parsing extended lan- guages. Specifically, the parse tables at the heart of traditional LALR(1) parsers are so monolithic and tightly constructed that, in the general case, it is impossible to extend them without regenerating them from the source grammar. Current extensible frameworks employ a variety of solutions, ranging from a full regeneration to using pluggable binary mod- ules for each different extension. But recompilation is time-consuming, while the pluggable modules in many cases cannot support the addition of more than one extension, or use backtracking or non-deterministic parsing techniques. We present here a middle-ground approach that allows an extension, if it meets certain restrictions, to be compiled into a parse table fragment. The host language parse table and fragments from multiple extensions can then always be efficiently composed to produce a conflict-free parse table for the extended language. This allows for the distribution of de- terministic parsers for extensible languages in a pre-compiled format, eliminating the need for the “source code” grammar to be distributed. In practice, we have found these restrictions to be reasonable and admit many useful language extensions. 1 Introduction In parsing programming languages, the usual practice is to generate a single parser for the language to be parsed. A well known and often-used approach is LR parsing [1] which relies on a process, sometimes referred to as grammar compilation, to generate a monolithic parse table representing the grammar being parsed.
    [Show full text]
  • Basics of Compiler Design
    Basics of Compiler Design Anniversary edition Torben Ægidius Mogensen DEPARTMENT OF COMPUTER SCIENCE UNIVERSITY OF COPENHAGEN Published through lulu.com. c Torben Ægidius Mogensen 2000 – 2010 [email protected] Department of Computer Science University of Copenhagen Universitetsparken 1 DK-2100 Copenhagen DENMARK Book homepage: http://www.diku.dk/∼torbenm/Basics First published 2000 This edition: August 20, 2010 ISBN 978-87-993154-0-6 Contents 1 Introduction 1 1.1 What is a compiler? . 1 1.2 The phases of a compiler . 2 1.3 Interpreters . 3 1.4 Why learn about compilers? . 4 1.5 The structure of this book . 5 1.6 To the lecturer . 6 1.7 Acknowledgements . 7 1.8 Permission to use . 7 2 Lexical Analysis 9 2.1 Introduction . 9 2.2 Regular expressions . 10 2.2.1 Shorthands . 13 2.2.2 Examples . 14 2.3 Nondeterministic finite automata . 15 2.4 Converting a regular expression to an NFA . 18 2.4.1 Optimisations . 20 2.5 Deterministic finite automata . 22 2.6 Converting an NFA to a DFA . 23 2.6.1 Solving set equations . 23 2.6.2 The subset construction . 26 2.7 Size versus speed . 29 2.8 Minimisation of DFAs . 30 2.8.1 Example . 32 2.8.2 Dead states . 34 2.9 Lexers and lexer generators . 35 2.9.1 Lexer generators . 41 2.10 Properties of regular languages . 42 2.10.1 Relative expressive power . 42 2.10.2 Limits to expressive power . 44 i ii CONTENTS 2.10.3 Closure properties . 45 2.11 Further reading .
    [Show full text]
  • Deterministic Parsing of Languages with Dynamic Operators
    Deterministic Parsing of Languages with Dynamic Op erators Kjell Post Allen Van Gelder James Kerr Baskin Computer Science Center University of California Santa Cruz, CA 95064 email: [email protected] UCSC-CRL-93-15 July 27, 1993 Abstract Allowing the programmer to de ne op erators in a language makes for more readable co de but also complicates the job of parsing; standard parsing techniques cannot accommo date dynamic grammars. We presentan LR parsing metho dology, called deferreddecision parsing , that handles dynamic op erator declarations, that is, op erators that are declared at run time, are applicable only within a program or context, and are not in the underlying language or grammar. It uses a parser generator that takes pro duction rules as input, and generates a table-driven LR parser, much like yacc. Shift/reduce con icts that involve dynamic op erators are resolved at parse time rather than at table construction time. For an op erator-rich language, this technique reduces the size of the grammar needed and parse table pro duced. The added cost to the parser is minimal. Ambiguous op erator constructs can either b e detected by the parser as input is b eing read or avoided altogether by enforcing reasonable restrictions on op erator declarations. Wehave b een able to describ e the syntax of Prolog, a language known for its lib eral use of op erators, and Standard ML, which supp orts lo cal declarations of op erators. De nite clause grammars DCGs, a novel parsing feature of Prolog, can b e translated into ecient co de by our parser generator.
    [Show full text]
  • Context-Aware Scanning and Determinism-Preserving Grammar Composition, in Theory and Practice
    Context-Aware Scanning and Determinism-Preserving Grammar Composition, in Theory and Practice A THESIS SUBMITTED TO THE FACULTY OF THE GRADUATE SCHOOL OF THE UNIVERSITY OF MINNESOTA BY August Schwerdfeger IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR THE DEGREE OF DOCTOR OF PHILOSOPHY July, 2010 c August Schwerdfeger 2010 ALL RIGHTS RESERVED Acknowledgments I would like to thank all my colleagues in the MELT group for all their input and assis- tance through the course of the project, and especially for their help in providing ready- made tests and applications for my software. Thanks specifically to Derek Bodin and Ted Kaminski for their efforts in integrating the Copper parser generator into MELT’s attribute grammar tools; to Lijesh Krishnan for developing the ableJ system of Java ex- tensions and assisting me extensively with its further development; and to Yogesh Mali for implementing and testing the Promela grammar with Copper. I also thank my advisor, Eric Van Wyk, for his continuous guidance throughout my time as a student, and also for going well above and beyond the call of duty in helping me to edit and prepare this thesis for presentation. I thank the members of my thesis committee, Mats Heimdahl, Gopalan Nadathur, and Wayne Richter, for their time and efforts in serving and reviewing. I especially wish to thank Prof. Nadathur for his many detailed questions and helpful suggestions for improving this thesis. Work on this thesis has been partially funded by National Science Foundation Grants 0347860 and 0905581. Support has also been received from funds provided by the Institute of Technology (soon to be renamed the College of Science and Engi- neering) and the Department of Computer Science and Engineering at the University of Minnesota.
    [Show full text]
  • An Efficient Context-Free Parsing Algorithm for Natural Languages1
    An Efficient Context-free Parsing Algorithm For Natural Languages1 Masaru Tomita Computer Science Department Carnegie-Mellon University Pittsburgh, PA 15213 Abstract because those algorithms are not tuned for any particular subset of context-free grammars, and must be able to handle all difficult This paper introduces an efficient context-free parsing phenomena in context-free grammars. In other words, they do algorithm and emphasizes its practical value in natural not take advantage of inherent features of the programming language processing. The algorithm can be viewed as an language. Intuitively speaking, algorithms in this group are extended LR parsing algorithm which embodies the concept efficient for "hard" grammars by sacrificing efficiency on "easy" of a "graph-structured stack." Unlike the standard LR, the grammars. algorithm is capable of handling arbitrary non cyclic context-free grammars including ambiguous grammars, No parsing algorithm has been designed that takes advantage while most of the LR parsing efficiency is preserved. The of inherent features of natural languages. Because natural algorithm seems more efficient than any existing algorithms languages include slightly more difficult phenomena than including the Cocke Younger Kasami algorithm and Earley's programming languages, we cannot simply use the first group of algorithm, as far as practical natural language parsing is algorithms for natural languages. Natural languages are a little concerned, due to utilization of LR parsing tables. The "harder" than programming languages, but they are still much algorithm is an all-path parsing algorithm; it produces all "easier" than general context-free languages As we have seen possible parse trees (a parse forest) in an efficient above, we have context-free parsing algorithms at two extremes.
    [Show full text]
  • Comp 411 Principles of Programming Languages Lecture 3 Parsing
    Comp 411 Principles of Programming Languages Lecture 3 Parsing Corky Cartwright January 29, 2021 Top Down Parsing • What is a context-free grammar (CFG)? • A recursive definition of a set of strings; it is identical in format to recursive data definitions of algebraic types (as in Ocaml or Haskell) except for the fact that it defines sets of strings using concatenation rather than sets of trees (objects/structs) using tree construction. The root symbol of a grammar generates the language of the grammar. In other words, it designates the string syntax of complete programs. • Example. The language of expressions generated by <expr> <expr> ::= <term> | <term> + <expr> <term> ::= <number> | <variable> | ( <expr> ) • Some sample strings generated by this CFG 5 5+10 5+10+7 (5+10)+7 • What is the fundamental difference between generating strings and generating trees? • The construction of a generated tree is manifest in the structure of the tree. • The construction of a generated string is not manifest in the structure of the string; it must be reconstructed by the parsing process. This reconstruction may be ambiguous and it may be costly in the general case (O(n3)). Fortunately, parsing the language for deterministic (LL(k), LR(k)) grammars is linear. Top Down Parsing cont. • We restrict our attention to LL(k) grammars because they can be parsed deterministically using a top-down approach. Every LL(k) grammar is LR(k). LR(k) grammars are those that can be parsed deterministically bottom-up using k- symbol lookahead. For every LL(k) grammar, there is an equivalent LR(1) grammar.
    [Show full text]
  • Head-Driven Transition-Based Parsing with Top-Down Prediction
    Head-driven Transition-based Parsing with Top-down Prediction Katsuhiko Hayashi†, Taro Watanabe‡, Masayuki Asahara§, Yuji Matsumoto† †Nara Institute of Science and Technology Ikoma, Nara, 630-0192, Japan ‡National Institute of Information and Communications Technology Sorakugun, Kyoto, 619-0289, Japan §National Institute for Japanese Language and Linguistics Tachikawa, Tokyo, 190-8561, Japan [email protected], [email protected] [email protected], [email protected] Abstract To improve parsing flexibility in deterministic parsing, our top-down parser uses beam search al- This paper presents a novel top-down head- gorithm with dynamic programming (Huang and driven parsing algorithm for data-driven pro- Sagae, 2010). The complexity becomes O(n2 b) jective dependency analysis. This algorithm ∗ handles global structures, such as clause and where b is the beam size. To reduce prediction er- coordination, better than shift-reduce or other rors, we propose a lookahead technique based on a bottom-up algorithms. Experiments on the FIRST function, inspired by the LL(1) parser (Aho English Penn Treebank data and the Chinese and Ullman, 1972). Experimental results show that CoNLL-06 data show that the proposed algo- the proposed top-down parser achieves competitive rithm achieves comparable results with other results with other data-driven parsing algorithms. data-driven dependency parsing algorithms. 2 Definition of Dependency Graph 1 Introduction A dependency graph is defined as follows. Transition-based parsing algorithms, such as shift- Definition 2.1 (Dependency Graph) Given an in- reduce algorithms (Nivre, 2004; Zhang and Clark, put sentence W = n0 ... nn where n0 is a spe- 2008), are widely used for dependency analysis be- cial root node $, a directed graph is defined as cause of the efficiency and comparatively good per- GW = (VW ,AW ) where VW = 0, 1, .
    [Show full text]
  • 9 Deterministic Top-Down Parsing
    Compilers and Compiler Generators © P.D. Terry, 2000 9 DETERMINISTIC TOP-DOWN PARSING In this chapter we build on the ideas developed in the last one, and discuss the relationship between the formal definition of the syntax of a programming language, and the methods that can be used to parse programs written in that language. As with so much else in this text, our treatment is introductory, but detailed enough to make the reader aware of certain crucial issues. 9.1 Deterministic top-down parsing The task of the front end of a translator is, of course, not the generation of sentences in a source language, but the recognition of them. This implies that the generating steps which led to the construction of a sentence must be deduced from the finished sentence. How difficult this is to do depends on the complexity of the production rules of the grammar. For Pascal-like languages it is, in fact, not too bad, but in the case of languages like Fortran and C++ it becomes quite complicated, for reasons that may not at first be apparent. Many different methods for parsing sentences have been developed. We shall concentrate on a rather simple, and yet quite effective one, known as top-down parsing by recursive descent, which can be applied to Pascal, Modula-2, and many similar languages, including the simple one of section 8.7. The reason for the phrase "by recursive descent" will become apparent later. For the moment we note that top- down methods effectively start from the goal symbol and try to regenerate the sentence by applying a sequence of appropriate productions.
    [Show full text]
  • The CYK Algorithm Informatics 2A: Lecture 20
    The CYK Algorithm Informatics 2A: Lecture 20 Adam Lopez 3 November 2016 1 / 32 1 Problems with Parsing as Search The need for ambiguity The computational cost of ambiguity 2 The CYK Algorithm Parsing as intersection Parsing as Dynamic Programming The CYK Algorithm Properties of the Algorithm 2 / 32 Problems with parsers we've learned so far Deterministic parsing can address grammars with limited ambiguity. For example, LL(1) parsing can handle grammars with no ambiguity. By re-structuring the grammar, the parser can make a unique decision, based on a limited amount of look-ahead. Recursive Descent parsing also demands grammar restructuring, in order to eliminate left-recursive rules that can get it into a hopeless loop. Can we avoid recursion and/ or ambiguity? 3 / 32 Left Recursion But grammars for natural human languages should be revealing, re-structuring the grammar may destroy this. (Indirectly) left-recursive rules are needed in English. NP ! DET N NP ! NPR DET ! NP 's These rules generate NPs with possessive modifiers such as: John's sister John's mother's sister John's mother's uncle's sister John's mother's uncle's sister's niece 4 / 32 Left Recursion NP NP NP DET N DET N DET N NP NP NP NPR DET N DET N NP NP John 's sister mother 's sister uncle 's sister NPR DET N NP John 's mother 's NPR John 's We don't want to re-structure our grammar rules just to be able to use a particular approach to parsing. Need an alternative.
    [Show full text]
  • LNCS 9031, Pp
    Faster, Practical GLL Parsing Ali Afroozeh and Anastasia Izmaylova Centrum Wiskunde & Informatica, 1098 XG Amsterdam, The Netherlands {ali.afroozeh, anastasia.izmaylova}@cwi.nl Abstract. Generalized LL (GLL) parsing is an extension of recursive- descent (RD) parsing that supports all context-free grammars in cubic time and space. GLL parsers have the direct relationship with the gram- mar that RD parsers have, and therefore, compared to GLR, are easier to understand, debug, and extend. This makes GLL parsing attractive for parsing programming languages. In this paper we propose a more efficient Graph-Structured Stack (GSS) for GLL parsing that leads to significant performance improve- ment. We also discuss a number of optimizations that further improve the performance of GLL. Finally, for practical scannerless parsing of pro- gramming languages, we show how common lexical disambiguation filters canbeintegratedinGLLparsing. Our new formulation of GLL parsing is implemented as part of the Iguana parsing framework. We evaluate the effectiveness of our approach using a highly-ambiguous grammar and grammars of real programming languages. Our results, compared to the original GLL, show a speedup factor of 10 on the highly-ambiguous grammar, and a speedup factor of 1.5, 1.7, and 5.2 on the grammars of Java, C#, and OCaml, respectively. 1 Introduction Developing efficient parsers for programming languages is a difficult task that is usually automated by a parser generator. Since Knuth’s seminal paper [1] on LR parsing, and DeRemer’s work on practical LR parsing (LALR) [2], parsers of many major programming languages have been constructed using LALR parser generators such as Yacc [3].
    [Show full text]