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

On Sunday 28 January 2007 11:34, Nick Roberts wrote:
>  > > 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);
>  > 
>  > And have casts from void* to the right type? I'm not sure that's any
>  > advantage.
> 
> Maybe using making a cast is as sinful as using a goto statement, I wouldn't
> know, but I would call having four times fewer functions an advantage.

"functions"? You mean having just one function pointer in language_specific? Yes,
I agree that would be superiour and I plan to make such a change, separately.

> Perhaps it would be better to use a macro e.g
> 
> #define name_of_child(var, index)   \
> (char *) (*var->root->lang->describe_child) (CHILD_NAME, var, index)

I'm not sure, I don't quite see reason to introduce macros if we can 
avoid them.

- Volodya




  reply	other threads:[~2007-01-29 10:53 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       ` -var-info-path-expression Nick Roberts
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             ` Vladimir Prus [this message]
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=200701291353.02239.ghost@cs.msu.su \
    --to=ghost@cs.msu.su \
    --cc=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=nickrob@snap.net.nz \
    /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