Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: Daniel Jacobowitz <drow@false.org>, 	gdb-patches@sources.redhat.com
Subject: Re: -var-info-path-expression
Date: Sun, 28 Jan 2007 00:46:00 -0000	[thread overview]
Message-ID: <17851.62039.333484.886195@kahikatea.snap.net.nz> (raw)
In-Reply-To: <200701280048.37153.ghost@cs.msu.su>

 >  c_describe_child (struct varobj *parent, int index,
 > -		  char **cname, struct value **cvalue, struct type **ctype)
 > +		  char **cname, struct value **cvalue, struct type **ctype,
 > +		  char **cfull_expression)

This argument list gets longer but, apart from only parent and index, only
one argument is non-null at any one time.  Would it be better to have

enum varobj_child_properties
  {
    CHILD_NAME,
    CHILD_VALUE,
    CHILD_TYPE,
    CHILD_FULL_EXPRESSION
  }

static void *
c_describe_child (enum varobj_child_properties property,
                  struct varobj *parent, int index)

and propagate these changes back to struct language_specific so we have:

static char *
name_of_child (struct varobj *var, int index)
{
  return (char *) (*var->root->lang->describe_child) (CHILD_NAME, var, index);
}

etc?

-- 
Nick                                           http://www.inet.net.nz/~nickrob


  reply	other threads:[~2007-01-28  0:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-25  9:02 -var-info-path-expression Vladimir Prus
2007-01-03 22:39 ` -var-info-path-expression Daniel Jacobowitz
2007-01-05  9:14   ` -var-info-path-expression Vladimir Prus
2007-01-27 21:49     ` -var-info-path-expression Vladimir Prus
2007-01-28  0:46       ` Nick Roberts [this message]
2007-01-28  7:57         ` -var-info-path-expression Vladimir Prus
2007-01-28  8:35           ` -var-info-path-expression Nick Roberts
2007-01-29 10:53             ` -var-info-path-expression Vladimir Prus
2007-01-29 12:17       ` -var-info-path-expression Daniel Jacobowitz
2007-06-18 10:43 -var-info-path-expression Vladimir Prus
2007-06-18 19:40 ` -var-info-path-expression Eli Zaretskii
2007-06-21  5:15   ` -var-info-path-expression Vladimir Prus
2007-07-03 17:14 ` -var-info-path-expression Daniel Jacobowitz
2007-07-03 17:51   ` -var-info-path-expression Vladimir Prus
2007-07-03 17:58     ` -var-info-path-expression Daniel Jacobowitz
2007-08-22 11:23 -var-info-path-expression Vladimir Prus
2007-08-22 15:28 ` -var-info-path-expression Daniel Jacobowitz
2007-08-28 17:18 ` -var-info-path-expression Vladimir Prus
2007-08-28 19:55   ` -var-info-path-expression Eli Zaretskii
2007-08-31  9:08   ` -var-info-path-expression Eli Zaretskii
2007-08-31  9:57     ` -var-info-path-expression Vladimir Prus
2007-08-31 18:04       ` -var-info-path-expression Eli Zaretskii
2007-08-31 18:53         ` -var-info-path-expression Vladimir Prus
2007-09-01  7:56           ` -var-info-path-expression Eli Zaretskii

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=17851.62039.333484.886195@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=ghost@cs.msu.su \
    /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