public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vgeddes at gnome dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug objc/32995]  New: False warning when implementing an instance method called `dealloc'
Date: Sun, 05 Aug 2007 13:54:00 -0000	[thread overview]
Message-ID: <bug-32995-14943@http.gcc.gnu.org/bugzilla/> (raw)

uname -a:
Linux ubuntu 2.6.20-16-generic #2 SMP Thu Jun 7 19:00:28 UTC 2007 x86_64
GNU/Linux

gcc -v:
Target: x86_64-linux-gnu
Configured with: ../src/configure -v
--enable-languages=c,c++,fortran,objc,obj-c++,treelang --prefix=/usr
--enable-shared --with-system-zlib --libexecdir=/usr/lib
--without-included-gettext --enable-threads=posix --enable-nls
--program-suffix=-4.1 --enable-__cxa_atexit --enable-clocale=gnu
--enable-libstdcxx-debug --enable-mpfr --enable-checking=release
x86_64-linux-gnu
Thread model: posix
gcc version 4.1.2 (Ubuntu 4.1.2-0ubuntu4)

command line and warning:
 gcc -DHAVE_CONFIG_H -I. -I.. -DG_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED
-DGDK_PIXBUF_DISABLE_DEPRECATED -DGCONF_DISABLE_DEPRECATED
-DGNOME_VFS_DISABLE_DEPRECATED -DLIBGLADE_DISABLE_DEPRECATED
-DPANGO_DISABLE_DEPRECATED -DGNOME_DISABLE_DEPRECATED -DPNG_NO_MMX_CODE
-I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0
-I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0
-I/usr/lib/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/libpng12
-Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare
-fconstant-string-class=IString -fobjc-exceptions -g -O2 -MT
libobjective_gnome_1_0_la-IObject.lo -MD -MP -MF
.deps/libobjective_gnome_1_0_la-IObject.Tpo -c IObject.m  -fPIC -DPIC -o
.libs/libobjective_gnome_1_0_la-IObject.o
IObject.m:65: warning: method possibly missing a [super dealloc] call


I have implemented an object `IObject' which subclasses the `Object' class
included the default Objective-C GNU runtime.

For stylistic compatibility with the Cocoa and GNUstep frameworks, I have
implemented a method called `dealloc' on `IObject'. `Object' does not define
this method.

When compiling this `IObject', I get this warning:
IObject.m:18: warning: method possibly missing a [super dealloc] call

Now, there is no `dealloc' method on `Object', so the warning is false. I
understand that the warning makes sense when using Cocoa or GNUstep, because
their root objects all have `dealloc' defined. But this is not the case for the
default GNU runtime.

Maybe we should define `dealloc' on `Object'?


-- 
           Summary: False warning when implementing an instance method
                    called `dealloc'
           Product: gcc
           Version: 4.1.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: objc
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: vgeddes at gnome dot org
GCC target triplet: x86_64-linux-gnu


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


             reply	other threads:[~2007-08-05 13:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-05 13:54 vgeddes at gnome dot org [this message]
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

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=bug-32995-14943@http.gcc.gnu.org/bugzilla/ \
    --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).