Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: Adam Fedor <fedor@doc.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Objective-C language support.
Date: Thu, 07 Nov 2002 23:44:00 -0000	[thread overview]
Message-ID: <vt24rascyeb.fsf@zenia.red-bean.com> (raw)
In-Reply-To: <3DAB86E8.2040704@doc.com>


Looks good to me.

Adam Fedor <fedor@doc.com> writes:

> Jim Blandy wrote:
> > The function stabsread_objc_colon should be static to stabsread.c, no?
> > If that's so, then it should be renamed to something like
> > `find_name_end', with a comment above the strchr ('[') != 0 case
> > explaining its relevance to Objective-C.  Since this function gets
> > called on every symbol, it's not an Objective-C specific function;
> > only part of it is.
> > The code needs a comment.  Most of GDB's maintainers don't know
> > Objective-C, so it would be helpful just to say something like,
> > "Objective-C symbols can have names like -[foo:bar:baz]:skun
> 
> Updated patch:
> 
> 2002-10-14  Adam Fedor  <fedor@gnu.org>
> 
> 	* stabsread.c (find_name_end): New function.
> 	(define_symbol): Use it.
> 
> 
> 
> 
> -- 
> Adam Fedor, Digital Optics Corp.      | I'm glad I hate spinach, because
> http://www.doc.com                    | if I didn't, I'd eat it, and you
>                                        | know how I hate the stuff.
> Index: stabsread.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/stabsread.c,v
> retrieving revision 1.42
> diff -u -p -r1.42 stabsread.c
> --- stabsread.c	11 Oct 2002 14:02:38 -0000	1.42
> +++ stabsread.c	15 Oct 2002 03:06:03 -0000
> @@ -169,6 +169,8 @@ static int
>  read_cfront_member_functions (struct field_info *, char **,
>  			      struct type *, struct objfile *);
>  
> +static char *find_name_end (char *name);
> +
>  /* end new functions added for cfront support */
>  
>  static void
> @@ -1271,7 +1273,7 @@ define_symbol (CORE_ADDR valu, char *str
>  	       struct objfile *objfile)
>  {
>    register struct symbol *sym;
> -  char *p = (char *) strchr (string, ':');
> +  char *p = (char *) find_name_end (string);
>    int deftype;
>    int synonym = 0;
>    register int i;
> @@ -2004,7 +2006,8 @@ define_symbol (CORE_ADDR valu, char *str
>           a typedef for "foo".  Unfortunately, cfront never makes the typedef
>           when translating C++ into C.  We make the typedef here so that
>           "ptype foo" works as expected for cfront translated code.  */
> -      else if (current_subfile->language == language_cplus)
> +      else if ((current_subfile->language == language_cplus)
> +	       || (current_subfile->language == language_objc))
>  	synonym = 1;
>  
>        SYMBOL_TYPE (sym) = read_type (&p, objfile);
> @@ -5613,6 +5616,32 @@ finish_global_stabs (struct objfile *obj
>        patch_block_stabs (global_symbols, global_stabs, objfile);
>        xfree (global_stabs);
>        global_stabs = NULL;
> +    }
> +}
> +
> +static char *
> +find_name_end (char *name)
> +{
> +  char *s = name;
> +  /* Find the end of the name, deliminated by a ':', but don't match
> +     ObjC symbols which look like -[Foo bar::]:bla.  */
> +  if (s[0] == '-' || *s == '+')
> +    {
> +      /* Must be an ObjC method symbol.  */
> +      if (s[1] != '[')
> +	{
> +	  error ("invalid symbol name \"%s\"", name);
> +	}
> +      s = strchr (s, ']');
> +      if (s == NULL)
> +	{
> +	  error ("invalid symbol name \"%s\"", name);
> +	}
> +      return strchr (s, ':');
> +    }
> +  else
> +    {
> +      return strchr (s, ':');
>      }
>  }
>  


  parent reply	other threads:[~2002-11-08  7:44 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-18  8:24 Adam Fedor
2002-09-18 10:50 ` Michael Snyder
2002-09-18 11:57   ` Michael Snyder
2002-09-18 11:57   ` Andrew Cagney
2002-09-18 12:04     ` Michael Snyder
2002-09-18 12:14       ` Andrew Cagney
2002-09-18 12:17         ` Michael Snyder
2002-09-18 13:51           ` Adam Fedor
2002-09-18 15:00             ` Michael Snyder
2002-09-18 15:19               ` Adam Fedor
2002-09-18 15:25               ` Andrew Cagney
2002-09-18 11:59   ` Daniel Berlin
2002-09-18 13:31   ` Adam Fedor
2002-09-18 14:03 ` Andrew Cagney
2002-10-08 16:36 ` Michael Snyder
2002-10-11 19:29   ` Adam Fedor
2002-10-08 16:42 ` Michael Snyder
2002-10-11 19:44   ` Adam Fedor
2002-10-21 15:18   ` Andrew Cagney
2002-10-21 15:27     ` Michael Snyder
2002-10-08 16:45 ` Michael Snyder
2002-10-11 19:39   ` Adam Fedor
2002-10-08 16:51 ` Michael Snyder
2002-10-14 13:06   ` Jim Blandy
2002-10-21 15:28     ` Andrew Cagney
2002-10-22 17:04       ` Michael Snyder
2002-10-22 18:42         ` Elena Zannoni
2002-10-08 16:58 ` Michael Snyder
2002-10-14 19:18   ` Adam Fedor
2002-10-21 15:31   ` Andrew Cagney
2002-10-08 17:01 ` Michael Snyder
2002-10-14 13:08   ` Jim Blandy
2002-10-18 10:06     ` Adam Fedor
2002-10-08 17:05 ` Michael Snyder
2002-10-14 13:14   ` Jim Blandy
2002-10-14 20:09     ` Adam Fedor
2002-10-18 14:24       ` Elena Zannoni
2002-10-22  5:49         ` Jim Blandy
2002-10-22 14:23           ` Michael Snyder
2002-10-21 15:25       ` Andrew Cagney
2002-11-07 23:44       ` Jim Blandy [this message]
2002-11-08  7:16         ` Elena Zannoni
2002-10-08 17:07 ` Michael Snyder
2002-10-11 20:06   ` Adam Fedor
2002-10-08 17:14 ` Michael Snyder
2002-10-13 18:51   ` Adam Fedor
2002-10-08 17:16 ` Michael Snyder
2002-10-12 11:37   ` Adam Fedor
2002-10-08 17:19 ` Michael Snyder
2002-10-14 19:33   ` Adam Fedor
2002-10-16 12:16     ` Michael Snyder
2002-10-08 17:30 ` Michael Snyder
2002-10-13 19:06   ` Adam Fedor
2002-10-21 15:35   ` Andrew Cagney
2002-10-21 16:19     ` Michael Snyder
2002-10-23 12:23     ` Michael Snyder
2002-10-23 12:36       ` Andrew Cagney
2002-10-23 13:10         ` Daniel Jacobowitz
2002-10-23 14:37           ` Michael Snyder
2002-10-23 14:35         ` Michael Snyder
2002-10-08 17:34 ` Michael Snyder
2002-10-13 19:12   ` Adam Fedor

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=vt24rascyeb.fsf@zenia.red-bean.com \
    --to=jimb@redhat.com \
    --cc=fedor@doc.com \
    --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