• 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 design question
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Class design question


  • Subject: Re: Class design question
  • From: Andy Armstrong <email@hidden>
  • Date: Sun, 13 Feb 2005 20:04:45 +0000

On 13 Feb 2005, at 19:36, Ken Tozier wrote:
Indexing is the part I do have solidly worked out. The basic conundrum was: Do I use the easier to maintain (and highly bloated) one class for each type, or go the more obscure, yet highly compact, function pointer route. I'm equally comfortable with either but if this project gets to a decent state, I'm thinking of open sourcing it and want to make it friendly enough that other programmers won't be completely confused.

I'd be inclined to implement an engine that treats the records as chunks of binary data and get all that working and then you can layer any kind of serialisation mechanism you want on top of it.


--
Andy Armstrong, hexten.net

_______________________________________________
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: 
 >Class design question (From: Ken Tozier <email@hidden>)
 >Re: Class design question (From: Jason Jobe <email@hidden>)
 >Re: Class design question (From: Ken Tozier <email@hidden>)
 >Re: Class design question (From: Jason Jobe <email@hidden>)
 >Re: Class design question (From: Ken Tozier <email@hidden>)
 >Re: Class design question (From: Andy Armstrong <email@hidden>)
 >Re: Class design question (From: Ken Tozier <email@hidden>)

  • Prev by Date: Re: Class design question
  • Next by Date: Re: Class design question
  • Previous by thread: Re: Class design question
  • Next by thread: Re: Class design question
  • Index(es):
    • Date
    • Thread