• 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: [Q] omissible method declaration in interface file
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Q] omissible method declaration in interface file


  • Subject: Re: [Q] omissible method declaration in interface file
  • From: Conor Dearden <email@hidden>
  • Date: Sat, 27 May 2006 10:50:35 +0200

This is why it's good habit not to omit method declarations. All your gripes
are addressed by the compiler, you can set the settings as strict as you
want. By default it will complain of a missing declaration, implement a
method and then make a call to that method without declaring it. The code
will run but Xcode will warn you that it can't find your method. People with
really good habits will go as far as including the delegate methods they
implement in the class header and even separate them into different
implementation declarations. You are going to need someone more experienced
then me to tell you why, but it's obvious it makes objective-C more flexible
and probably has to do with one or all of the following: delegation,
categories, protocols, class cluster and other fun class behaviours that
objective-C has.

Conor
http://www.bruji.com/


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Prev by Date: Live Sorting a NSTreeController
  • Next by Date: Re: Writing out a BOOL value to a .plist
  • Previous by thread: [Q] omissible method declaration in interface file
  • Next by thread: RE: [Q] omissible method declaration in interface file
  • Index(es):
    • Date
    • Thread