public inbox for archer-commits@sourceware.org
help / color / mirror / Atom feed
From: tromey@sourceware.org
To: archer-commits@sourceware.org
Subject: [SCM]  archer-tromey-multi-inferior: change itsets to use {...} rather than [...] this avoids a possible conflict with Objective C
Date: Wed, 06 Oct 2010 18:03:00 -0000	[thread overview]
Message-ID: <20101006180301.10010.qmail@sourceware.org> (raw)

The branch, archer-tromey-multi-inferior has been updated
       via  e82998171e6f93d200699bedc6189a731bcef332 (commit)
      from  6a834dee4e74b60ae9b6692f5d40f4df007ddd11 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email.

- Log -----------------------------------------------------------------
commit e82998171e6f93d200699bedc6189a731bcef332
Author: Tom Tromey <tromey@redhat.com>
Date:   Wed Oct 6 12:02:18 2010 -0600

    change itsets to use {...} rather than [...]
    this avoids a possible conflict with Objective C

-----------------------------------------------------------------------

Summary of changes:
 gdb/itset.c |   14 +++++++-------
 1 files changed, 7 insertions(+), 7 deletions(-)

First 500 lines of diff:
diff --git a/gdb/itset.c b/gdb/itset.c
index c35374c..164ef42 100644
--- a/gdb/itset.c
+++ b/gdb/itset.c
@@ -488,15 +488,15 @@ itset_create (const char **specp)
   struct cleanup *cleanups;
   const char *spec = *specp;
 
-  if (*spec != '[')
-    error (_("I/T set must start with `['"));
+  if (*spec != '{')
+    error (_("I/T set must start with `{'"));
 
   result = XCNEW (struct itset);
   result->refc = 1;
 
   cleanups = make_cleanup (itset_cleanup, result);
 
-  /* Skip the '['.  */
+  /* Skip the '{'.  */
   ++spec;
   spec = skip_whitespace (spec);
 
@@ -520,13 +520,13 @@ itset_create (const char **specp)
       spec = skip_whitespace (spec);
       if (*spec == ',')
 	++spec;
-      else if (*spec == ']')
+      else if (*spec == '}')
 	break;
       else
-	error (_("',' or ']' expected in I/T set, at `%s'"), spec);
+	error (_("',' or '}' expected in I/T set, at `%s'"), spec);
     }
 
-  /* Skip the ']'.  */
+  /* Skip the '}'.  */
   ++spec;
 
   result->spec = xstrndup (*specp, spec - *specp);
@@ -553,7 +553,7 @@ itset_create (const char **specp)
 struct itset *
 itset_create_current (void)
 {
-  const char *spec = "[!current]";
+  const char *spec = "{!current}";
 
   return itset_create (&spec);
 }


hooks/post-receive
--
Repository for Project Archer.


                 reply	other threads:[~2010-10-06 18:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20101006180301.10010.qmail@sourceware.org \
    --to=tromey@sourceware.org \
    --cc=archer-commits@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).