• 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: Replacing objects
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Replacing objects


  • Subject: Re: Replacing objects
  • From: "Kyle Sluder" <email@hidden>
  • Date: Mon, 22 Dec 2008 19:04:28 -0500

On Mon, Dec 22, 2008 at 6:03 PM, WT <email@hidden> wrote:
> Of course,
> the proxy object's class has to share the same interface as the class of the
> objects it represents so that your code doesn't need to know whether it's
> dealing with a proxy or with the real thing.

This isn't true in Objective-C.  Take a look at NSProxy, the canonical
implementation of the very pattern you're describing.  To state this
is to completely miss the characteristics that define Objective-C.

Like Ken said, you're probably doing something very wrong.

--Kyle Sluder
_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Replacing objects
      • From: WT <email@hidden>
References: 
 >Re: Replacing objects (From: WT <email@hidden>)

  • Prev by Date: Re: NSStream APIs
  • Next by Date: Debugging memory smashers with GC
  • Previous by thread: Re: Replacing objects
  • Next by thread: Re: Replacing objects
  • Index(es):
    • Date
    • Thread