public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Doug Evans <xdje42@gmail.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/5] cp-namespace.c cleanup pass: whitespace
Date: Wed, 17 Dec 2014 09:24:00 -0000	[thread overview]
Message-ID: <m3oar2d40a.fsf@sspiff.org> (raw)
In-Reply-To: <m34msxihmn.fsf@seba.sebabeach.org> (Doug Evans's message of	"Sun, 14 Dec 2014 21:53:04 -0800")

Doug Evans <xdje42@gmail.com> writes:
> Hi.
>
> Part 1 is just whitespace to get it out of the way.
>
> 2014-12-14  Doug Evans  <xdje42@gmail.com>
>
> 	* cp-namespace.c: Whitespace cleanup.

Hi.
Here is a revised patch for current HEAD.

2014-12-17  Doug Evans  <xdje42@gmail.com>

	* cp-namespace.c: Whitespace cleanup.

diff --git a/gdb/cp-namespace.c b/gdb/cp-namespace.c
index f17cd69..bcb2275 100644
--- a/gdb/cp-namespace.c
+++ b/gdb/cp-namespace.c
@@ -95,7 +95,6 @@ cp_scan_for_anonymous_namespaces (const struct symbol *const symbol,
     }
 }
 
-
 /* Add a using directive to using_directives.  If the using directive
    in question has already been added, don't add it twice.
 
@@ -121,7 +120,7 @@ cp_add_using_directive (const char *dest,
 {
   struct using_direct *current;
   struct using_direct *new;
-  
+
   /* Has it already been added?  */
 
   for (current = using_directives; current != NULL; current = current->next)
@@ -227,7 +226,7 @@ lookup_symbol_file (const char *name,
 	 So we only search the current file's global block.  */
 
       const struct block *global_block = block_global_block (block);
-      
+
       if (global_block != NULL)
 	sym = lookup_symbol_in_block (name, global_block, domain);
     }
@@ -388,7 +387,7 @@ cp_lookup_symbol_via_imports (const char *scope,
   if (!declaration_only)
     sym = cp_lookup_symbol_in_namespace (scope, name,
 					 block, domain, 1);
-  
+
   if (sym != NULL)
     return sym;
 
@@ -532,7 +531,7 @@ cp_lookup_symbol_imports_or_template (const char *scope,
       /* Search the function's template parameters.  */
       if (SYMBOL_IS_CPLUS_TEMPLATE_FUNCTION (function))
 	{
-	  struct template_symbol *templ 
+	  struct template_symbol *templ
 	    = (struct template_symbol *) function;
 
 	  result = search_symbol_list (name,
@@ -613,10 +612,10 @@ cp_lookup_symbol_imports_or_template (const char *scope,
   return result;
 }
 
- /* Searches for NAME in the current namespace, and by applying
-    relevant import statements belonging to BLOCK and its parents.
-    SCOPE is the namespace scope of the context in which the search is
-    being evaluated.  */
+/* Searches for NAME in the current namespace, and by applying
+   relevant import statements belonging to BLOCK and its parents.
+   SCOPE is the namespace scope of the context in which the search is
+   being evaluated.  */
 
 struct symbol*
 cp_lookup_symbol_namespace (const char *scope,
@@ -819,6 +818,7 @@ find_symbol_in_baseclass (struct type *parent_type, const char *name,
   sym = NULL;
   concatenated_name = NULL;
   cleanup = make_cleanup (free_current_contents, &concatenated_name);
+
   for (i = 0; i < TYPE_N_BASECLASSES (parent_type); ++i)
     {
       size_t len;

      reply	other threads:[~2014-12-17  9:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-15  5:54 Doug Evans
2014-12-17  9:24 ` Doug Evans [this message]

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=m3oar2d40a.fsf@sspiff.org \
    --to=xdje42@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).