This is the mail archive of the
mailing list for the GCC project.
Re: PATCH: cp/parse.y -> cp/cp-parse.in
- From: Jason Merrill <jason at redhat dot com>
- To: Ziemowit Laski <zlaski at apple dot com>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Wed, 05 Dec 2001 11:04:33 +0000
- Subject: Re: PATCH: cp/parse.y -> cp/cp-parse.in
- References: <B11D291C-E900-11D5-92F8-0030658361CA@apple.com>
>>>>> "Ziemowit" == Ziemowit Laski <email@example.com> writes:
> Also, having cp/cp-parse.in instead of cp/parse.y in the FSF tree
> will allow the C++ front-end to become more "isomorphic" (pardon my
> group theory) to the C front-end. Bringing the C and C++ front-ends
> closer together in this way should not only reduce the ongoing
> maintenance burden, but also make it easier to switch over to a
> unified front-end in the future.
FYI, work is proceeding on a new recursive-descent parser for C++;
hopefully the yacc parser won't be around much longer. Certainly it will
go away before the frontends are unified. You folks should probably take a
look at the cp-parser-branch.