From: Michael Elizabeth Chastain <mec@shout.net>
To: drow@mvista.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch] testsuite/gdb.c++/local.exp: accept more nested types
Date: Mon, 27 May 2002 13:09:00 -0000 [thread overview]
Message-ID: <200205271934.g4RJYKc28203@duracef.shout.net> (raw)
Hi Daniel,
> I think that I (as C++ maintainer rather than testsuite maintainer)
> need to figure out what the correct output is.
Well, actually, the manual should specify the output of ptype,
and you should implement the manual, and I should test to the manual.
Without a written spec, we have to thrash this out among ourselves.
> "InnerLocal::NestedInnerLocal nest1" is not actually valid C++ in
> general, I don't believe; what if there is a class
> InnerLocal::InnerLocal::NestedInnerLocal?
Fortunately for us, that is not legal C++. gcc 2.96-rh and gcc 3.1
both give me a "duplicate nested type" error.
I admit this is a technicality. But for purposes of human readability,
it means that "InnerLocal::NestedInnerLocal nest1" will behave according
to the expectations of a reasonable human reader.
> This is also uglier; for std:: types there's going to be a lot of
> useless noise.
It's useful noise if the user has their own type with the same name
as a std:: type.
> By this logic, InnerLocal::NestedInnerLocal deserves a KFAIL comment
> for the moment, since the code to do this is not yet present.
I don't think it's a failure at all.
Frankly, if we do decide it's a failure, I'd rather just leave it as
a FAIL for a while. I don't want to add a bunch more regular expressions
and file a bug report just to make it a different kind of failure.
We're at an impasse here ... does anyone else have an opinion?
Michael C
next reply other threads:[~2002-05-27 19:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-27 13:09 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-27 11:38 Michael Elizabeth Chastain
2002-05-27 11:41 ` Daniel Jacobowitz
2002-05-27 11:07 Michael Elizabeth Chastain
2002-05-27 11:12 ` Daniel Jacobowitz
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=200205271934.g4RJYKc28203@duracef.shout.net \
--to=mec@shout.net \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.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