From: "Marc Khouzam" <marc.khouzam@ericsson.com>
To: "Nick Roberts" <nickrob@snap.net.nz>
Cc: <gdb-patches@sourceware.org>
Subject: RE: [Patch] -var-evaluate-expression NAME [FORMAT]
Date: Wed, 23 Jan 2008 14:30:00 -0000 [thread overview]
Message-ID: <6D19CA8D71C89C43A057926FE0D4ADAA04290E54@ecamlmw720.eamcs.ericsson.se> (raw)
In-Reply-To: <18326.44682.805865.581205@kahikatea.snap.net.nz>
> > I kind of cheated and used NULL to indicate that the format used should be
> > the one stored in the varobj structure.
>
> I would use a new function, e.g., something like
>
> char *
> varobj_get_formatted_value (struct varobj *var,
> enum varobj_display_formats format)
> {
> enum varobj_display_formats oldformat;
> char* value;
> oldformat = var->format;
> var->format = format;
> value = varobj_get_value (var);
> var->format = oldformat;
> return value;
> }
>
> and call it when argc == 2 in mi_cmd_var_evaluate_expression so that you
> don't have to change all calls to varobj_get_value and related functions.
> (Note: not tested)
I hadn't thought of temporarily setting var->format, instead of passing 'format'
everywhere. Much easier! Is there any way that varob_get_value() could not return?
Like a failed gdb_assert? Or are we sure that var->format will be reset to
the old format properly no matter what happens to varobj_get_value?
> > +/* Parse a string argument into a format value. */
> > +
> > +static enum varobj_display_formats
> > +mi_parse_format (const char *arg)
> > +{
> > + int len;
> > +
> > + len = strlen (arg);
> > +
> > + if (strncmp (arg, "natural", len) == 0)
> > + return FORMAT_NATURAL;
> > + else if (strncmp (arg, "binary", len) == 0)
> > + return FORMAT_BINARY;
> > + else if (strncmp (arg, "decimal", len) == 0)
> > + return FORMAT_DECIMAL;
> > + else if (strncmp (arg, "hexadecimal", len) == 0)
> > + return FORMAT_HEXADECIMAL;
> > + else if (strncmp (arg, "octal", len) == 0)
> > + return FORMAT_OCTAL;
> > + else
> > + error (_("Unknown display format: must be: \"natural\", \"binary\", \"decimal\", \"hexadecimal\", or \"octal\""));
> > +}
> > +
>
> and I would refactor this out of mi_cmd_var_set_format.
Didn't I do that already?
next prev parent reply other threads:[~2008-01-23 14:30 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-22 20:38 Marc Khouzam
2008-01-23 3:04 ` Nick Roberts
2008-01-23 14:30 ` Marc Khouzam [this message]
2008-01-23 14:42 ` Daniel Jacobowitz
2008-01-23 17:04 ` Marc Khouzam
2008-01-23 22:09 ` Nick Roberts
2008-01-24 21:36 ` Marc Khouzam
2008-01-25 9:59 ` Eli Zaretskii
2008-01-29 21:45 ` Daniel Jacobowitz
2008-02-01 19:23 ` Marc Khouzam
2008-02-02 10:31 ` Eli Zaretskii
2008-02-03 19:43 ` Marc Khouzam
2008-02-03 20:01 ` Eli Zaretskii
2008-02-04 14:17 ` Marc Khouzam
2008-02-04 21:00 ` Eli Zaretskii
2008-02-02 11:20 ` Vladimir Prus
2008-02-03 19:55 ` Marc Khouzam
2008-02-03 20:42 ` Joel Brobecker
2008-02-03 21:41 ` Daniel Jacobowitz
2008-02-03 21:46 ` Daniel Jacobowitz
2008-02-04 17:00 ` Marc Khouzam
2008-02-04 17:02 ` Marc Khouzam
2008-02-04 21:40 ` Nick Roberts
2008-02-04 21:53 ` Nick Roberts
2008-02-05 14:47 ` Marc Khouzam
2008-02-05 20:43 ` Nick Roberts
2008-02-05 20:55 ` Marc Khouzam
2008-02-05 21:18 ` Nick Roberts
2008-02-04 17:11 ` Marc Khouzam
2008-01-23 3:48 ` Daniel Jacobowitz
2008-01-23 14:44 ` Marc Khouzam
2008-01-28 14:41 Marc Khouzam
2008-01-28 14:48 ` 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=6D19CA8D71C89C43A057926FE0D4ADAA04290E54@ecamlmw720.eamcs.ericsson.se \
--to=marc.khouzam@ericsson.com \
--cc=gdb-patches@sourceware.org \
--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