Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: Adam Fedor <fedor@doc.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Objective-C language support.
Date: Tue, 08 Oct 2002 16:42:00 -0000	[thread overview]
Message-ID: <3DA36D31.2947E451@redhat.com> (raw)
In-Reply-To: <3D889A97.90202@doc.com>

Adam Fedor wrote:
> 
> This patch adds Objective-C language support to gdb based upon a patch
> provided by Apple Computer Inc from their version of gdb. Note that the
> patch only contains changes to existing files. New files (objc-lang.h,
> objc-lang.c, objc-exp.y) and a gdb.objc testsuite directory are located at
> 
> ftp://ftp.gnustep.org/pub/gnustep/contrib/gdb-objc-patch.tar.gz

Adam, this bit can't hurt anything, since it just adds some new enum
values.  Only one suggestion -- how about putting OP_THIS and OP_SELF
consecutively, because they're so similar?  Also please hold off on
the export of evaluate_subexp -- let's handle that separately.

Other than that, approved.  Wait a couple days for objections, then
you can commit it.


>         * expression.h: New ops NSSTRING, SELECTOR, MSGCALL, and SELF.

> Index: gdb/expression.h
> ===================================================================
> RCS file: /cvs/src/src/gdb/expression.h,v
> retrieving revision 1.4
> diff -u -p -r1.4 expression.h
> --- gdb/expression.h    1 Aug 2002 17:18:32 -0000       1.4
> +++ gdb/expression.h    17 Sep 2002 19:30:05 -0000
> @@ -181,6 +181,12 @@ enum exp_opcode
>         making three exp_elements.  */
>      OP_FUNCALL,
> 
> +    /* OP_MSGCALL is followed by a string in the next exp_element and then an
> +       integer.  The string is the selector string.  The integer is the number
> +       of arguments to the message call.  That many plus one values are used,
> +       the first one being the object pointer.  This is an Objective C message */
> +    OP_MSGCALL,
> +
>      /* This is EXACTLY like OP_FUNCALL but is semantically different.
>         In F77, array subscript expressions, substring expressions
>         and function calls are  all exactly the same syntactically. They may
> @@ -273,11 +279,17 @@ enum exp_opcode
>      STRUCTOP_STRUCT,
>      STRUCTOP_PTR,
> 
> -    /* C++ */
> -    /* OP_THIS is just a placeholder for the class instance variable.
> +    /* C++: OP_THIS is just a placeholder for the class instance variable.
>         It just comes in a tight (OP_THIS, OP_THIS) pair.  */
>      OP_THIS,
> 
> +    /* Objective C: "@selector" pseudo-operator */
> +    OP_SELECTOR,
> +
> +    /* Objective-C: OP_SELF is just a placeholder for the class instance
> +       variable.  It just comes in a tight (OP_SELF, OP_SELF) pair.  */
> +    OP_SELF,
> +
>      /* OP_SCOPE surrounds a type name and a field name.  The type
>         name is encoded as one element, but the field name stays as
>         a string, which, of course, is variable length.  */
> @@ -305,7 +317,10 @@ enum exp_opcode
>      OP_NAME,
> 
>      /* An unparsed expression.  Used for Scheme (for now at least) */
> -    OP_EXPRSTRING
> +    OP_EXPRSTRING,
> +
> +    /* An Objective C Foundation Class NSString constant */
> +    OP_NSSTRING,
>    };
> 
>  union exp_element
> @@ -369,6 +384,10 @@ enum noside
> 
>  extern struct value *evaluate_subexp_standard
>    (struct type *, struct expression *, int *, enum noside);
> +
> +extern struct value *evaluate_subexp (struct type *, struct expression *,
> +                                     int *, enum noside);
> +
> 
>  /* From expprint.c */
>


  parent reply	other threads:[~2002-10-08 23:42 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   ` 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:57   ` Michael Snyder
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 [this message]
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
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=3DA36D31.2947E451@redhat.com \
    --to=msnyder@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