• 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: Multiple inheritance and objective-c
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Multiple inheritance and objective-c


  • Subject: Re: Multiple inheritance and objective-c
  • From: Serge Meynard <email@hidden>
  • Date: Mon, 21 Mar 2005 19:37:42 -0500

If A has nothing to do with C, yet B (a subclass of A) shares 90% of its code with C... That sounds a bit crooked to me :)
Can you have B and C both inherit from a shared class D, then have A be a subclass of B? Or simply have A and C inherit from D, and skip B altogether?



On Mar 21, 2005, at 19:09, Mark Dawson wrote:

Maybe I wasn't clear--class A's functionality has nothing to with C's. The shared functionality has to with what B is adding to A (via the subclass).

_______________________________________________ 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
References: 
 >Multiple inheritance and objective-c (From: Mark Dawson <email@hidden>)
 >Re: Multiple inheritance and objective-c (From: "John C. Warner" <email@hidden>)
 >Re: Multiple inheritance and objective-c (From: Mark Dawson <email@hidden>)
 >Re: Multiple inheritance and objective-c (From: Mont Rothstein <email@hidden>)
 >Re: Multiple inheritance and objective-c (From: Mark Dawson <email@hidden>)

  • Prev by Date: Re: newbie EXC_BAD_ACCESS
  • Next by Date: Re: Multiple inheritance and objective-c
  • Previous by thread: Re: Multiple inheritance and objective-c
  • Next by thread: Re: Multiple inheritance and objective-c
  • Index(es):
    • Date
    • Thread