Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: [VxWorks 01/20] fix parameter names in cli/cli-utils.h
Date: Fri, 04 Mar 2011 06:22:00 -0000	[thread overview]
Message-ID: <1299219720-13398-2-git-send-email-brobecker@adacore.com> (raw)
In-Reply-To: <1299219720-13398-1-git-send-email-brobecker@adacore.com>

The declaration used "inp" as the name of the parameter for the two
skip_spaces/skip_to_space routines, whereas the implementation used
"chp".  I reconciled the two using "chp" (seems slightly more
intuitive, and also less work ;-) ).

gdb/ChangeLog:

        * cli/cli-utils.h (skip_spaces, skip_to_space): Rename parameter
        from "inp" to "chp" to be in sync with implementation.  Update
        documentation accordingly.
---
 gdb/cli/cli-utils.h |   12 ++++++------
 1 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/gdb/cli/cli-utils.h b/gdb/cli/cli-utils.h
index 09240d0..8f0b46e 100644
--- a/gdb/cli/cli-utils.h
+++ b/gdb/cli/cli-utils.h
@@ -55,14 +55,14 @@ extern int get_number_or_range (char **);
 
 extern int number_is_in_list (char *list, int number);
 
-/* Skip leading whitespace characters in INP, returning an updated
-   pointer.  If INP is NULL, return NULL.  */
+/* Skip leading whitespace characters in CHP, returning an updated
+   pointer.  If CHP is NULL, return NULL.  */
 
-extern char *skip_spaces (char *inp);
+extern char *skip_spaces (char *chp);
 
-/* Skip leading non-whitespace characters in INP, returning an updated
-   pointer.  If INP is NULL, return NULL.  */
+/* Skip leading non-whitespace characters in CHP, returning an updated
+   pointer.  If CHP is NULL, return NULL.  */
 
-extern char *skip_to_space (char *inp);
+extern char *skip_to_space (char *chp);
 
 #endif /* CLI_UTILS_H */
-- 
1.7.0.4


  reply	other threads:[~2011-03-04  6:22 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-04  6:22 Add support for VxWorks (v3) Joel Brobecker
2011-03-04  6:22 ` Joel Brobecker [this message]
2011-03-04  6:22 ` [VxWorks 03/20] New toplevel_command_post observer Joel Brobecker
2011-03-04  6:22 ` [VxWorks 04/20] New general purpose routines in utils.c Joel Brobecker
2011-03-04  6:22 ` [VxWorks 05/20] more parsing routines in cli/cli-utils Joel Brobecker
2011-03-04  6:22 ` [VxWorks 02/20] Some ada-lang/ada-tasks routines needed by the VxWorks target Joel Brobecker
2011-03-04  6:23 ` [VxWorks 10/20] Add options to control Vxworks related settings Joel Brobecker
2011-03-04  6:23 ` [VxWorks 06/20] add new "unload" command (symetry of existing "load" command) Joel Brobecker
2011-03-04  6:23 ` [VxWorks 08/20] New modules gdb_dlfcn and remote-wtx-utils Joel Brobecker
2011-03-04  6:23 ` [VxWorks 07/20] new struct bp_target_info target_private_data field Joel Brobecker
2011-03-04  6:24 ` [VxWorks 09/20] remote-wtxapi: The WTX API abstraction layer Joel Brobecker
2011-03-04  6:24 ` [VxWorks 11/20] VxWorks breakpoint-handling module Joel Brobecker
2011-03-04  6:24 ` [VxWorks 14/20] remote-wtx-hw: register fetch/store support Joel Brobecker
2011-03-04  6:24 ` [VxWorks 12/20] "multi-tasks-mode" support Joel Brobecker
2011-03-04  6:24 ` [VxWorks 13/20] Add partition support Joel Brobecker
2011-03-04  6:25 ` [VxWorks 17/20] Add support for VxWorks 6 Joel Brobecker
2011-03-04  6:25 ` [VxWorks 19/20] Configury and Makefile updates for VxWorks Joel Brobecker
2011-03-04  6:25 ` [VxWorks 15/20] Add new "wtx" target Joel Brobecker
2011-03-04  6:25 ` [VxWorks 18/20] Add tdep files for x86 and powerpc Joel Brobecker
2011-03-04  6:25 ` [VxWorks 16/20] WTX-TCL support module Joel Brobecker
2011-03-04  6:25 ` [VxWorks 20/20] document the new VxWorks port Joel Brobecker
2011-03-04  9:36 ` Add support for VxWorks (v3) Pedro Alves
2011-03-04 10:05   ` Joel Brobecker
2011-03-04 10:45     ` Pedro Alves
2011-03-04 12:10       ` Joel Brobecker
2011-03-07 19:49 ` Tom Tromey

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=1299219720-13398-2-git-send-email-brobecker@adacore.com \
    --to=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