• 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: class cluster making: easy/lazy way to keep counterpart methods in sync?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: class cluster making: easy/lazy way to keep counterpart methods in sync?


  • Subject: Re: class cluster making: easy/lazy way to keep counterpart methods in sync?
  • From: Ondra Cada <email@hidden>
  • Date: Sat, 21 Feb 2004 23:44:57 +0100

On Saturday, Feb 21, 2004, at 23:13 Europe/Prague, Ben Dougall wrote:

Moving the methods which are same for all classes into the abstract superclass, perhaps?

similar, not identical methods. like the NSNumber class that's on the usual class cluster apple documentation page -- a class cluster because the requirements for storage varies. and the ivars go in the subclasses as do the methods that access them.

Maybe you could show a concrete piece of code?

Seems to me you have two kinds of methods: ones which can go up (since they don't depend on the storage details), and ones which you would never want to "edit in more places at once", so to speak. What am I overlooking?
---
Ondra Hada
OCSoftware: email@hidden http://www.ocs.cz
private email@hidden http://www.ocs.cz/oc
_______________________________________________
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.
References: 
 >Re: class cluster making: easy/lazy way to keep counterpart methods in sync? (From: Ben Dougall <email@hidden>)

  • Prev by Date: Zlib compression
  • Next by Date: Re: class cluster making: easy/lazy way to keep counterpart methods in sync?
  • Previous by thread: Re: class cluster making: easy/lazy way to keep counterpart methods in sync?
  • Next by thread: Re: class cluster making: easy/lazy way to keep counterpart methods in sync?
  • Index(es):
    • Date
    • Thread