This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: PATCH: cp/parse.y -> cp/cp-parse.in
Jason Merrill wrote:
>
> >>>>> "Ziemowit" == Ziemowit Laski <zlaski@apple.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.
We have looked at it, and it's very exciting, but we can't use
anything on a branch; it's enough work just to do regular imports
from the trunk. Also, the new parser does not have an expected
completion date, while we're madly working to shift from using 2.95
to 3.1 as the new OS X system compiler.
Stan