Re: Looking for editors and parsers for C++

xorian@solomon.technet.sg (Xorian Technologies)
Mon, 27 Jul 1992 01:43:18 GMT

          From comp.compilers

Related articles
Looking for editors and parsers for C++ Jan.Skarvall@eua.ericsson.se (1992-07-23)
Re: Looking for editors and parsers for C++ xorian@solomon.technet.sg (1992-07-27)
| List of all articles for this month |
Newsgroups: comp.lang.c++,comp.editors,comp.compilers
From: xorian@solomon.technet.sg (Xorian Technologies)
Organization: National University of Singapore
Date: Mon, 27 Jul 1992 01:43:18 GMT
References: 92-07-076
Keywords: C++, parse

Jan Skarvall write :-


: I am also interested in parsers and parser generators for C++ for the same
: reasons.


Our parser generator LADE is able to generate a C++ parser with 0
shift-reduce and 0 reduce-reduce conflicts. We are also in the process of
writing a C++ parser which will be ready soon.


: We are currently using C++ 2.1.


As far as the parser is concerned there is little difference between 2.1
and 3.0, since template and exception handling has more impact on the code
generation part.


: [Jim Roskind's yacc C++ parser is available in the compilers archives, but
: I'm not sure that'd much help for building an editor. -John]


The problem with Roskind's grammar is that in order to resolve the many
significant ambiguities in C++, Roskind "macro expanded" the productions
involved. While he resolved most of the conflicts, he created monster of a
grammar which bears little resemblance to the specification and is
extremely difficult to use in practice. Based on our own experience and
that of our clients, we strongly recommend against the Roskind grammar for
anything more than simple syntactic checking.


KG Loh
Xorian Technologies Pte Ltd
389A Balestier Road
Singapore 1232
Republic of Singapore
Tel: (65) 255-7151
Fax: (65) 253-7709
email: xorian@solomon.technet.sg
--


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.