• 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
Interface declarations necessary?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Interface declarations necessary?


  • Subject: Interface declarations necessary?
  • From: Francisco Tolmasky <email@hidden>
  • Date: Sat, 14 Feb 2004 02:36:20 -0800

Are interface declarations necessary? I have a sort of class clusters situation where I have the main class and one or two subclasses that have very slight differences which are actually returned. Neither of them have extra member variables, so I would really like to just write the implementation. I tried just skipping the interface declaration and it seemed to work, all I got was a warning but it ran fine. Is there an "accepted" way to do this? Are there any hidden pitfalls in doing this?

basically i did this:

@implementaiton myclass: rootclass

- (void)yo
{
//crazy stuff
}

@end

Francisco Tolmasky
email@hidden
http://users.adelphia.net/~ftolmasky
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: Interface declarations necessary?
      • From: "Louis C. Sacha" <email@hidden>
  • Prev by Date: Re: Combining Binding and Drag & Drop in TableView
  • Next by Date: Re: Framework causing a problem
  • Previous by thread: Re: NSImage and flipping
  • Next by thread: Re: Interface declarations necessary?
  • Index(es):
    • Date
    • Thread