Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Klee Dienes <kdienes@apple.com>
Cc: Daniel Jacobowitz <drow@mvista.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Function return type checking
Date: Tue, 12 Mar 2002 07:56:00 -0000	[thread overview]
Message-ID: <3C8E250C.4070601@cygnus.com> (raw)
In-Reply-To: <3B4ED0FE-35A5-11D6-A901-0030653FA4C6@apple.com>


>> Is this feature intended for C or ObjectiveC developers?

> 
> I'd intend for this to be used by everyone. We specifically added it in response to bug reports from people making heavy use of the system math libraries; as well as from Cocoa (Objective-C) developers making heavy use of functions returning NSRect objects. The reason it's of interest to me in preparing the Objective-C patches is that much of the Objective-C GDB code makes use of being able to pass 'expected_type' arguments to the modified functions, and I'd rather not have to re-architect all those calls before submitting the patches.

So there are two reasons for the change?  The infrastructure you need 
for objective C and a user visible interface change.  Can you expand a 
little on the objective C problems.  If objective C has good reason for 
this infrastructure than I can't see why that part shouldn't go in.

enjoy,
Andrew



  reply	other threads:[~2002-03-12 15:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-05  1:36 Klee Dienes
2002-02-05  3:24 ` Eli Zaretskii
2002-02-05  8:07 ` Daniel Jacobowitz
2002-02-06 13:43   ` Klee Dienes
2002-02-06 14:14     ` Daniel Jacobowitz
2002-03-09 20:30     ` Andrew Cagney
2002-03-12  2:38       ` Klee Dienes
2002-03-12  7:56         ` Andrew Cagney [this message]
2002-03-12 10:08           ` Klee Dienes
2002-03-12 10:34             ` Andrew Cagney
2002-02-08 13:41 ` Kevin Buettner

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=3C8E250C.4070601@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kdienes@apple.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