From: Kevin Buettner <kevinb@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] More completion improvements
Date: Sun, 18 Feb 2001 08:40:00 -0000 [thread overview]
Message-ID: <1010218164030.ZM21263@ocotillo.lan> (raw)
In-Reply-To: <Pine.SUN.3.91.1010218092227.4804N-100000@is>
On Feb 18, 9:31am, Eli Zaretskii wrote:
> * solib.c (_initialize_solib): Ditto for `solib-search-path' and
> `solib-absolute-prefix'.
Eli,
Your solib.c changes are approved.
I have a minor style criticism. I would prefer to see function calls
with an embedded assignment expression written as a separate assignment
statement followed by the function call. E.g, instead of writing...
add_show_from_set
(c = add_set_cmd ("solib-absolute-prefix", class_support, var_filename,
(char *) &solib_absolute_prefix,
"Set prefix for loading absolute shared library symbol files.\n\
For other (relative) files, you can add values using `set solib-search-path'.",
&setlist),
&showlist);
...write this instead:
c = add_set_cmd ("solib-absolute-prefix", class_support, var_filename,
(char *) &solib_absolute_prefix,
"Set prefix for loading absolute shared library symbol files.\n\
For other (relative) files, you can add values using `set solib-search-path'.",
&setlist);
add_show_from_set (c, &showlist);
The GNU coding standards do not explicitly address this case, but they
do address a similar case regarding if-conditions. See:
http://www.gnu.org/prep/standards_24.html#SEC24
Kevin
next prev parent reply other threads:[~2001-02-18 8:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-12 0:18 [RFA] File-name " Eli Zaretskii
2001-02-14 10:35 ` Fernando Nasser
2001-02-15 3:13 ` Eli Zaretskii
2001-02-17 23:05 ` Eli Zaretskii
2001-02-17 23:34 ` [RFA] More " Eli Zaretskii
2001-02-18 6:58 ` Fernando Nasser
2001-02-18 7:58 ` Eli Zaretskii
2001-02-18 8:40 ` Kevin Buettner [this message]
2001-02-18 9:56 ` Fernando Nasser
2001-02-18 10:39 ` Kevin Buettner
2001-02-18 10:49 ` Fernando Nasser
2001-02-18 12:22 ` Eli Zaretskii
2001-02-19 3:48 ` 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=1010218164030.ZM21263@ocotillo.lan \
--to=kevinb@cygnus.com \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.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