• 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
Re: Redeclaring overrides
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Redeclaring overrides


  • Subject: Re: Redeclaring overrides
  • From: "John C. Randolph" <email@hidden>
  • Date: Sun, 19 Aug 2001 02:27:34 -0700

On Sunday, August 19, 2001, at 12:35 AM, Finlay Dobbie wrote:

On Sunday, August 19, 2001, at 03:00 am, Chris Gehlker wrote:

Well, that's just too short, at least for me. If there were a style that
said "Declare everything you define, even if it's an override" I could
understand. But that's not what "Learning Cocoa" is doing.

The real answer is probably that some of the people writing the sample code prefer to declare them, some of them don't. *shrug*

I personally normally don't bother.

I usually declare overrides in the header, just because it helps anyone reading my code to quickly see what I've changed from the superclass.

-jcr



For every complex problem there is an answer that is clear, simple, and wrong. -- H L Mencken


  • Follow-Ups:
    • Re: Redeclaring overrides
      • From: Ondra Cada <email@hidden>
References: 
 >Re: Redeclaring overrides (From: Finlay Dobbie <email@hidden>)

  • Prev by Date: Re: Redeclaring overrides
  • Next by Date: Re: Fax capabilities?
  • Previous by thread: Re: Redeclaring overrides
  • Next by thread: Re: Redeclaring overrides
  • Index(es):
    • Date
    • Thread