Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Michael Chastain <mec.gnu@mindspring.com>
Cc: gdb@sources.redhat.com, david.carlton@sun.com, carlton@bactrian.org
Subject: Re: new testsuite function for c++ ptype
Date: Tue, 03 Aug 2004 19:16:00 -0000	[thread overview]
Message-ID: <410FE479.1020104@gnu.org> (raw)
In-Reply-To: <410F9C94.nail8KU11N4AM@mindspring.com>

> Here is a sample.  Consider the C++ class:
> 
>   class A : virtual public V
>   {
>   public:
>     virtual int f();
>   private:
>     int a;
>   };
> 
> The call to test this is:
> 
>   cp_test_ptype_class "ptype A" "ptype A" \
>     "class" "VA" { "public virtual V" } \
>     { "V" } \
>     {
>       { "private" "int a;" }
>     } \
>     {
>       { "public" "virtual int f();" }
>     } \
>     ""

Yes, we desperatly need this.  Some random ideas.

- can the list of fields be grouped vis:

	.... {
	  {
	    { "private" "int a;" }
	  }
	  {
	    { "public" "virtual int f();" }
	  }
	} ...

so that the formatting / indentation looks more C++ like.

-  could, for fields and methods, they have explicit tag fields vis:

	{
	  { field private "int a;" }
	  { method public "virtual int f();" }
	}

or:

	{
	  field { private "int a;" }
	  method { public "virtual int f();" }
	}

so that there are more textual clues on what is going on (it's a very 
long parameter list)

- I don't undersand why "V" appears twice in:
 >     "class" "VA" { "public virtual V" } \
 >     { "V" } \
I guess I'm really asking if "V" can be extracted from "public virtual V"

Have fun.

Andrew



  reply	other threads:[~2004-08-03 19:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-03 14:09 Michael Chastain
2004-08-03 19:16 ` Andrew Cagney [this message]
2004-08-04  4:36   ` Michael Chastain

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=410FE479.1020104@gnu.org \
    --to=cagney@gnu.org \
    --cc=carlton@bactrian.org \
    --cc=david.carlton@sun.com \
    --cc=gdb@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