Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: David Carlton <carlton@math.stanford.edu>
Cc: gdb <gdb@sources.redhat.com>, Michael Elizabeth Chastain <mec@shout.net>
Subject: Re: [rfc] xfailed tests in gdb.c++/classes.exp
Date: Fri, 28 Feb 2003 01:30:00 -0000	[thread overview]
Message-ID: <20030228013013.GA20822@nevyn.them.org> (raw)
In-Reply-To: <ro18yy1lub7.fsf@jackfruit.Stanford.EDU>

Sorry for losing this message (again).

On Fri, Jan 03, 2003 at 02:53:00PM -0800, David Carlton wrote:
> I've been looking at the xfailed tests in gdb.c++/classes.exp, and
> some of the xfails aren't too convincing.  Specifically, the tests
> that I'm looking at do ptypes of C++ data structures, and several of
> the xfails fall into one or both of these categories:
> 
> 1) GDB prints "class X { public: ... }" when the programmer originally
>    wrote "struct X { ... }".

Hmm, this should definitely be eiter a pass or an XFAIL.  If you want
to let it pass, I'm fine with that decision.

> 2) GDB prints "class X { private: int x; ... }" when the programmer
>    originally wrote "class X { int x; ... }".

This should either be a PASS or be corrected.  Do you think that it's
more logical to print it as above or should we just elide the private?

I think we have already got logic to do this, so it might be an
outright bug that we don't.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-02-28  1:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-03 22:53 David Carlton
2003-02-28  1:30 ` Daniel Jacobowitz [this message]
2003-01-03 23:27 Michael Elizabeth Chastain
2003-02-28  3:51 Michael Elizabeth Chastain
2003-02-28  3:59 ` Daniel Jacobowitz
2003-02-28 13:40   ` Paul Koning
2003-02-28 20:58 ` Jason Molenda
2003-02-28  5:01 Michael Elizabeth Chastain
2003-02-28 15:15 ` Daniel Jacobowitz
2003-02-28 17:58   ` David Carlton

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=20030228013013.GA20822@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=carlton@math.stanford.edu \
    --cc=gdb@sources.redhat.com \
    --cc=mec@shout.net \
    /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