This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: New C++ Parser


>>>>> "Per" == Per Bothner <per@bothner.com> writes:

    Per> That is good news.  Other possible benefits (I don't know
    Per> enough to other than guess/hope):

All the things you mention are probably true.

    Per>   - If the C grammar is re-written as the same time, you can
    Per> perhaps share much of the code.

We do not plan to replace the C parser -- at this time -- but we do
plan to make that an easy thing to do in the future.  Gradually, I
want to see more and more of the front-ends combined.

    Per>   - Can use same grammer is other applications (such as gdb),
    Per> some of which might need a reentrant grammar, which is
    Per> difficult with yacc.  (A re-entrant grammar was a goal for
    Per> cppexp.c.)

Yes.

--
Mark Mitchell                   mark@codesourcery.com
CodeSourcery, LLC               http://www.codesourcery.com

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]