From: Simon Marchi <simon.marchi@ericsson.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Add comment for mi_run_cmd_full
Date: Thu, 22 May 2014 17:22:00 -0000 [thread overview]
Message-ID: <537E325D.4050908@ericsson.com> (raw)
In-Reply-To: <20140521222611.GQ22822@adacore.com>
On 14-05-21 06:26 PM, Joel Brobecker wrote:
> Hi Simon,
>
>> 2014-05-21 Simon Marchi <simon.marchi@ericsson.com>
>>
>> * lib/mi-support.exp (mi_run_cmd_full): Add comments.
>
> Overall, this looks good to me. I wasn't aware of the history,
> so just did a little bit of catching up :-), but I confirm that
> the description you propose matches the actual behavior...
>
>> +# use_mi_command selects whether MI or CLI commands are used by the
>> +# procedure.
>> +# args is passed to the command used to run the test program, "run" or
>> +# "-exec-run", depending on the value of use_mi_command. Therefore, if
>> +# use_mi_command is false, they are effectively args to the test program.
>> +# If use_mi_command is true, they are simply arguments to -exec-run.
>> proc mi_run_cmd_full {use_mi_command args} {
>> global suppress_flag
>> if { $suppress_flag } {
>> --
>> 2.0.0.rc0
>
> When speaking of the value of a variable, the variable name should be
> in all caps. For instance:
>
> # USE_MI_COMMAND selects whether MI or CLI commands are used by the
> # procedure.
Ok.
> If I may suggest a different approach (anyone is welcome to comment
> on that too), it'd be useful to succintly say what the function does
> first, before getting into the details of the parameters. Also, I would
> group the semantics of each value of use_mi_command together. So,
> one example:
>
> # Send the command to run the test program.
> #
> # If USE_MI_COMMAND is true, the "-exec-run" command is used.
> # Otherwise, the "run" (CLI) command is used.
> #
> # ARGS is passed as argument to the command used to run the test program.
> # Beware that arguments to "-exec-run" do not have the same semantics as
> # arguments to the "run" command, so USE_MI_COMMAND influences the meaning
> # of ARGS. If USE_MI_COMMAND is true, they are arguments to -exec-run.
> # If USE_MI_COMMAND is false, they are effectively arguments passed
> # to the test program.
>
> I hope it helps!
>
I think this is very clear. Should I post an updated patch ?
next prev parent reply other threads:[~2014-05-22 17:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-21 21:48 Simon Marchi
2014-05-21 22:26 ` Joel Brobecker
2014-05-22 17:22 ` Simon Marchi [this message]
2014-05-22 17:30 ` Joel Brobecker
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=537E325D.4050908@ericsson.com \
--to=simon.marchi@ericsson.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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