public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nicola at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug objc/32995] False warning when implementing an instance method called `dealloc'
Date: Tue, 14 Sep 2010 22:52:00 -0000	[thread overview]
Message-ID: <20100914225230.26686.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32995-14943@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from nicola at gcc dot gnu dot org  2010-09-14 22:52 -------
If you want to use dealloc for "compatibility" with Apple Cocoa / GNUstep Base,
then you also want the warnings that dealloc needs to include a call to [super
dealloc], so I wouldn't change the compiler ;-)

You could change your code though - if you're triyng to be compatible with
Cocoa / GNUstep, then you may as well define an NSObject root class and have a
dealloc method in it ;-)

If you still want to use Object, you can add a -dealloc method to Object by
using a category:

@interface Object (dealloc)
- (void) dealloc;
@end

(the add the implementation).  Then you can have the missing [super dealloc] in
your subclass, and the compiler won't generate any warnings.

Thanks


-- 

nicola at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |WONTFIX


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32995


      parent reply	other threads:[~2010-09-14 22:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-05 13:54 [Bug objc/32995] New: " vgeddes at gnome dot org
2007-08-05 13:56 ` [Bug objc/32995] " vgeddes at gnome dot org
2007-08-06 21:40 ` pinskia at gcc dot gnu dot org
2010-09-14 22:52 ` nicola at gcc dot gnu dot org [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=20100914225230.26686.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).