From: Michael Snyder <msnyder@specifix.com>
To: Yakov Lerner <iler.ml@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: simlpe patch implements eval command (with printf-like format and args)
Date: Thu, 21 Feb 2008 22:56:00 -0000 [thread overview]
Message-ID: <1203634223.19253.221.camel@localhost.localdomain> (raw)
In-Reply-To: <f36b08ee0802211437t1e01a7abq8811b4fe29982b7b@mail.gmail.com>
On Fri, 2008-02-22 at 00:37 +0200, Yakov Lerner wrote:
> On Fri, Feb 22, 2008 at 12:11 AM, Michael Snyder <msnyder@specifix.com> wrote:
> >
> > On Thu, 2008-02-21 at 11:20 +0200, Yakov Lerner wrote:
> > > This simple patch implements eval command with printf-like syntax:
> > >
> > > eval "printf-like-format", comma-separated args
> > >
> > > The patch is against cvs-checkedout source. Suggestions are welcome.
> > > Implementation is very simple.
> >
> > Not bad at all, for a first contribution. But I suggest
> > you try to limit the scope a little bit and make it still
> > simpler -- maybe have it accept only strings, floats and ints
> > to start -- and see if you can't implement it less intrusively
>
> You mean here, to replicate (with cuts) the code of existing
> printf_command(), and leave existing printf_command()
> unchanged, correct ?
That is in fact what I meant, but now I'm having second thoughts.
It's just that you're modifying print_command quite a lot.
If you factored out the grow/append functionality, could you
do it with more minimal changes to printf_command (or to, say,
printf_command_core()?)
Aside, is there any reason to put the new command in source.c?
Why not keep the code close together by putting it in printcmd.c?
Doesn't seem like it's directly related to source files...
next prev parent reply other threads:[~2008-02-21 22:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 17:33 Yakov Lerner
2008-02-21 22:37 ` Michael Snyder
2008-02-21 22:50 ` Yakov Lerner
2008-02-21 22:56 ` Michael Snyder [this message]
2008-02-22 9:59 ` Daniel Jacobowitz
2008-02-22 11:17 ` Yakov Lerner
2008-02-22 17:12 ` Eli Zaretskii
2008-02-24 15:39 ` Yakov Lerner
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=1203634223.19253.221.camel@localhost.localdomain \
--to=msnyder@specifix.com \
--cc=gdb-patches@sourceware.org \
--cc=iler.ml@gmail.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