<?xml version="1.0" standalone="yes"?>
<Paper uid="C94-1064">
  <Title>PARSING AS TREE TRAVERSAL</Title>
  <Section position="3" start_page="0" end_page="0" type="intro">
    <SectionTitle>
1 INTRODUCTION
</SectionTitle>
    <Paragraph position="0"> In this paper, I present a unified approach to parsing, in which top-down, bottom-up and left-corner parsers are related to preorder, postorder and in-order tree traversals. To some extent, this connection is already clear since for each parsing strategy the nodes of the parse tree are constructed according to the corresponding tree traversal. It is somewhat trickier though, to actually use a tree traversa.l program as a parser since the resulting pa.rser may be left recursive. This left recursion can *The research presented in this paper was partially sponsored by Teilprojekt Bd &amp;quot;Constraints on Grammar for Efficient Generation&amp;quot; of the Sonderforschungsbereich 340 of the Deutsche Forschungsgemeinschaft. I wouhl also like to thank Guido Minnen and Dieter Martini for helpflfl comments. All mistakes are of course my own.</Paragraph>
    <Paragraph position="1"> ?KI. Wilhelmstr. 113, D-72074 T(ibingen, Germany, dg@sfs.nphil.uni-tuebingen.de.</Paragraph>
    <Paragraph position="2"> be eliminated, however, by employing a version of Greibach Normal Form which is extended to handle argument instantiations in definite clause grammars.</Paragraph>
    <Paragraph position="3"> The resulting parsers resemble the standard Prolog versions of versions of such parsers. One can then go one step further and partially execute the parser with respect to a particular grammar--as is normally done with definite clause gra,,nn~a,'s (Per(,ir~ ~ Warren \[JO\]). a surprising result of this partial execution is l.ha.t the bottom-up and left-corner parsers become identical when they are 1)oth partially executed. This may explain why the BUP parser of ~/lil.tSllll\]OtO eta\]. \[6\] \[71 was ,'eferre.d tO as a bottona-u I) parser even though it clearly follows a left-corner strategy.</Paragraph>
  </Section>
class="xml-element"></Paper>