Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Michael Snyder <msnyder@specifix.com>
Cc: Vladimir Prus <ghost@cs.msu.su>, gdb-patches@sources.redhat.com
Subject: Re: [Patch] Try2: -var-evaluate-expression [-f FORMAT] NAME
Date: Wed, 02 Apr 2008 18:50:00 -0000	[thread overview]
Message-ID: <20080402181744.GA15035@caradoc.them.org> (raw)
In-Reply-To: <1207159695.31772.122.camel@localhost.localdomain>

On Wed, Apr 02, 2008 at 11:08:15AM -0700, Michael Snyder wrote:
> On Wed, 2008-04-02 at 17:22 +0400, Vladimir Prus wrote:
> > Marc Khouzam wrote:
> > 
> > > 2008-04-01  Marc Khouzam  <marc.khouzam@ericsson.com>
> > > 
> > >         * mi/mi-cmd-var.c: Include "mi-getopt.h".
> > >         (mi_parse_format): New.  Factored out from mi_cmd_var_set_format.
> > >         (mi_cmd_var_set_format): Use new mi_parse_format.
> > >         (mi_cmd_var_evaluate_expression): Support for -f option to specify
> > >         format.
> > >         * Makefile.in (mi-cmd-var.o): Update dependencies.
> > > 
> > >         * varobj.h (varobj_get_formatted_value): Declare.
> > >         * varobj.c (my_value_of_variable): Added format parameter.
> > >         (cplus_value_of_variable): Likewise.
> > >         (java_value_of_variable): Likewise.
> > >         (*(value_of_variable)): Likewise.
> > 
> > Is '*(value_of_variable)' really a name of a function? :-)
> 
> It is, actually -- but not in varobj.c.  Thanks for raising this.
> Marc, we prefer not to have identifiers or file names abbreviated
> in changelogs.

Context is:

  /* The current value of VAR. */
  char *(*value_of_variable) (struct varobj * var);

It's a member of struct language_specifick which is how we usually
attribute the changelog entry.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-04-02 18:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-01 14:33 Marc Khouzam
2008-04-02  0:17 ` Nick Roberts
2008-04-02 13:23   ` Marc Khouzam
2008-04-02 16:26 ` Vladimir Prus
2008-04-02 18:20   ` Michael Snyder
2008-04-02 18:50     ` Daniel Jacobowitz [this message]
2008-04-02 19:10     ` Marc Khouzam
2008-04-02 21:26   ` Marc Khouzam
2008-04-03  4:42     ` Nick Roberts
2008-04-04 15:07       ` Marc Khouzam
2008-04-06  6:42         ` OT: IDES [was RE: Re: [Patch] Try2: -var-evaluate-expression [-f FORMAT] NAME] Nick Roberts
2008-04-06 22:46           ` Daniel Jacobowitz
2008-04-04 15:17     ` [Patch] Try2: -var-evaluate-expression [-f FORMAT] NAME Vladimir Prus
2008-04-08 17:04 ` Marc Khouzam
2008-04-08 22:24   ` Eli Zaretskii
2008-04-09 14:54     ` Marc Khouzam

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=20080402181744.GA15035@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=ghost@cs.msu.su \
    --cc=msnyder@specifix.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