• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Redeclaring overrides
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Redeclaring overrides


  • Subject: Redeclaring overrides
  • From: Chris Gehlker <email@hidden>
  • Date: Sat, 18 Aug 2001 11:54:05 -0700

Toward the end of "Learning Cocoa" there is some advice to declare
awakeFromNib and isOpaque in the .h file of a sample application. The book
doesn't go into any detail about why you should redeclare methods that are
already in the headers. It certainly doesn't do this consistently.

I can't tell if this is just another "Learning Cocoa" brain fart or if there
is some semantic reason for redeclairing these methods analogous to the way
that declaring virtual destructors are used in C++ to signal when the class
is intended to be abstract. Would somebody please set me straight?

While I'm asking, does ObjC have a convention for signaling whether a class
is concrete?
--
C++: The power, elegance and simplicity of a hand grenade.


  • Follow-Ups:
    • Re: Redeclaring overrides
      • From: "David P. Henderson" <email@hidden>
    • Re: Redeclaring overrides
      • From: Georg Tuparev <email@hidden>
  • Prev by Date: Re: Downloading html page
  • Next by Date: Re: tcpdump wiggin out?
  • Previous by thread: Re: How to handle planar raw images ?
  • Next by thread: Re: Redeclaring overrides
  • Index(es):
    • Date
    • Thread