From: Martin von Loewis <martin@mira.isdn.cs.tu-berlin.de>
To: egcs@cygnus.com
Subject: Parsing templates as baseclasses
Date: Sun, 01 Mar 1998 16:07:00 -0000 [thread overview]
Message-ID: <199803012359.AAA06557@mira.isdn.cs.tu-berlin.de> (raw)
I'm trying to investigate the code
namespace foo {
template <class T>
class x {};
}
class y : public foo::x<int> {};
I've got the lexer to produce, for the last line
(AGGR `class') (IDENTIFIER_DEFN `y')
(':')(VISSPEC)
(NSNAME)(SCOPE)
(PTYPENAME `x')('<')(TYPESPEC `int')('>')
('{')
The last line is eventually reduced -> template_type.
Then I get an error with the stack
state stack now 0 1 4 66 222 223 466 717 958 123
In the non-namespace case, the template_type is further reduced
-> type_name -> nonnested_type -> base_class.1
Now, where should I put the support for namespace-qualified template
types? I'll have to eventually reduce this to baseclass.1 as well,
preferably without declaring foo::x<int> a nested type (it isn't).
Also, I'd like to avoid additional conflicts in the grammar.
Any guidance appreciated.
Martin
next reply other threads:[~1998-03-01 16:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-01 16:07 Martin von Loewis [this message]
1998-03-01 16:59 ` Mark Mitchell
1998-05-09 3:34 ` Martin von Loewis
1998-03-03 1:08 Mike Stump
1998-03-02 20:02 ` Mark Mitchell
1998-03-04 13:54 ` Neal Becker
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=199803012359.AAA06557@mira.isdn.cs.tu-berlin.de \
--to=martin@mira.isdn.cs.tu-berlin.de \
--cc=egcs@cygnus.com \
/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: link
Be 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).