• 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: NSMutableDictionaries as object implementation (was Re: Cocoa Bindings - nondebuggable, non-obvious, procedural ???)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSMutableDictionaries as object implementation (was Re: Cocoa Bindings - nondebuggable, non-obvious, procedural ???)


  • Subject: Re: NSMutableDictionaries as object implementation (was Re: Cocoa Bindings - nondebuggable, non-obvious, procedural ???)
  • From: Charlton Wilbur <email@hidden>
  • Date: Wed, 5 Jan 2005 21:29:17 -0500


On Jan 5, 2005, at 8:38 PM, Tim Lucas wrote:

On 06/01/2005, at 12:17 PM, Charlton Wilbur wrote:

On Jan 5, 2005, at 8:01 PM, Tim Lucas wrote:

I think the CocoaDevCentral article (1) on bindings is misleading people into thinking their objects should be dictionaries, and IMO it should be revised to eliminate the public NSMutableDictionary's. This implementation would be unacceptable in all but demonstration implementations.

Out of curiosity, why?

Yep there's nothing wrong with NSDictionary's as the internal storage mechanism.


The problem is copying the approach that the CocoaDevCentral article has taken and providing a public NSMutableDictionary [....]

OK, this makes sense, and I agree that it's a problem. But the problem isn't the use of NSMutableDictionaries (which is why I queried), it is the lack of encapsulation because of no accessor methods.


(For some reason, writing theoretical posts about object orientation is *much* more interesting than working on code tonight.)

I reckon! And we won't even start on asking what you meant by a "theoretical post" ;)

See the lengthy post in which I demonstrated that KVC can be used isomorphically to message sending. I felt like I was in graduate school again....


Charlton


-- Charlton Wilbur email@hidden email@hidden

_______________________________________________
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: 
 >Re: Cocoa Bindings - nondebuggable, non-obvious, procedural ??? (From: Philippe Mougin <email@hidden>)
 >Re: Cocoa Bindings - nondebuggable, non-obvious, procedural ??? (From: Charlton Wilbur <email@hidden>)
 >Re: Cocoa Bindings - nondebuggable, non-obvious, procedural ??? (From: Philippe Mougin <email@hidden>)
 >Re: Cocoa Bindings - nondebuggable, non-obvious, procedural ??? (From: Tim Lucas <email@hidden>)
 >NSMutableDictionaries as object implementation (was Re: Cocoa Bindings - nondebuggable, non-obvious, procedural ???) (From: Charlton Wilbur <email@hidden>)
 >Re: NSMutableDictionaries as object implementation (was Re: Cocoa Bindings - nondebuggable, non-obvious, procedural ???) (From: Tim Lucas <email@hidden>)

  • Prev by Date: calling Java for ObjC
  • Next by Date: Re: Cocoa Bindings - nondebuggable, non-obvious, procedural ???
  • Previous by thread: Re: NSMutableDictionaries as object implementation (was Re: Cocoa Bindings - nondebuggable, non-obvious, procedural ???)
  • Next by thread: Re: Cocoa Bindings - nondebuggable, non-obvious, procedural ???
  • Index(es):
    • Date
    • Thread