public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Akim Demaille <akim@epita.fr> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/7051: gcc/cp/parse.y & gcc/cp/decl.h: Conflict on TYPENAME + Yacc types clashes Date: Thu, 20 Jun 2002 04:14:00 -0000 [thread overview] Message-ID: <20020620104606.26316.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/7051; it has been noted by GNATS. From: Akim Demaille <akim@epita.fr> To: gcc-gnats@gcc.gnu.org Cc: nobody@gcc.gnu.org Subject: Re: c++/7051: gcc/cp/parse.y & gcc/cp/decl.h: Conflict on TYPENAME + Yacc types clashes Date: 20 Jun 2002 12:45:29 +0200 | >Category: c++ | >Responsible: unassigned | >Synopsis: gcc/cp/parse.y & gcc/cp/decl.h: Conflict on TYPENAME + Yacc types clashes | >Arrival-Date: Mon Jun 17 02:46:02 PDT 2002 This can be closed, fixed by: 2002-06-19 Akim Demaille <akim@epita.fr> * parse.y (TYPENAME): Rename as tTYPENAME to avoid the clash with decl.h's TYPENAME. * spew.c, lex.c: Adjust. * parse.y (explicit_instantiation): Add empty action to override the default $$ = $1 where it introduces a type clash.
next reply other threads:[~2002-06-20 10:46 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-06-20 4:14 Akim Demaille [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-06-24 7:57 lerdsuwa 2002-06-17 3:56 akim
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20020620104606.26316.qmail@sources.redhat.com \ --to=akim@epita.fr \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).