Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [cplus] An initial use of the canonicalizer
Date: Wed, 31 Dec 2003 14:04:00 -0000	[thread overview]
Message-ID: <20031231140419.GA31238@nevyn.them.org> (raw)
In-Reply-To: <20031231041140.CE4984B35A@berman.michael-chastain.com>

On Tue, Dec 30, 2003 at 11:11:40PM -0500, Michael Chastain wrote:
> > So if we're printing <int, 33> somewhere and <int,33> somewhere else,
> > that will be a bug.  So I'd write all the tests to match <int, 33> only.
> >
> > That's the theory I'm going by at the moment at least.
> 
> That's a point in favor of accepting only "<int,33>".
> 
> However, I'm going to need to check gdb 6.0 against gdb-6_1-branch
> eventually.  It will help if I can run some of the same test scripts
> from gdb-6_1-branch to check for regressions.  That's why I want
> "<int, ?33>", even though it fuzzes the test a little.
> 
> So I guess we're in disagreement here.

As I said, the choices are:
 - Being able to test vs. 6.1
 - Being able to verify that our output is consistently formatted

I guess I'll go with (A) until after the next GDB release and then
clean up any remaining formatting problems.  This makes the testsuite
less useful for my development so I'll probably do (B) in
drow-cplus-branch.

> And man is there a mountain of much worse problems in gdb.cp/*.exp
> right now.  I'm checking classes.exp and it's full of stuff like:
> 
>   "int i;{$ws};int j;.*\}\n$gdb_prompt$ "
> 
> Can you do anything about this:
> 
>   (gdb) ptype class whatever
>   type = class whatever {
>     public:
>       int i;
>       int j;
> 
>     public:
>       whatever & operator=(whatever const &);
>       whatever(whatever const &);
>       whatever();
>   }
> 
> The implicit functions appear with -gstabs+ and do not appear
> with -gdwarf-2.  This causes either a whole lot of extra pattern
> lines or a lot of "int j;.*\}".  I have low tolerance for ".*"
> in a test pattern!

It can't be fixed.  I spent a miserable long time last year trying. 
There's not enough information to figure out whether the constructor is
explicit or implicit.  Just write out the operators inside ()? instead,
in the testcase.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-12-31 14:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-31  4:12 Michael Elizabeth Chastain
2003-12-31 14:04 ` Daniel Jacobowitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-12-31 19:04 Michael Elizabeth Chastain
2004-01-01  6:03 ` Eli Zaretskii
2004-01-01  7:50   ` Daniel Jacobowitz
2003-12-31  2:26 Michael Elizabeth Chastain
2003-12-31  3:36 ` Daniel Jacobowitz
2003-12-31  1:43 Michael Elizabeth Chastain
2003-12-31  2:09 ` Daniel Jacobowitz
2003-12-30 21:15 Michael Elizabeth Chastain
2003-12-31  0:59 ` Daniel Jacobowitz
2003-12-30 21:03 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=20031231140419.GA31238@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec.gnu@mindspring.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