• 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: Object Copying Question
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Object Copying Question


  • Subject: Re: Object Copying Question
  • From: Andreas Mayer <email@hidden>
  • Date: Sat, 14 Sep 2002 16:21:56 +0200

Am Samstag, 14.09.02 um 15:49 Uhr schrieb Greg Hulands:

When doing the above, won't cellCopy only have enough memory for super, and that the memory for self will not have been allocated?

No.

Am i missing something here?

super does refer to the same object as self.
The only difference is that it tells the run-time system to use the method implementation of self's superclass.

Somewhere up the hierarchy the object will actually create a copy of the memory it occupies. That operation will take in count the actual size of the object, regardless of the way it was told to do so.

At least that is how I think I understood that Objective-C's OO system works. :)


bye. Andreas.
_______________________________________________
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: 
 >Object Copying Question (From: Greg Hulands <email@hidden>)

  • Prev by Date: Object Copying Question
  • Next by Date: setting the cell class for NSTextField
  • Previous by thread: Object Copying Question
  • Next by thread: setting the cell class for NSTextField
  • Index(es):
    • Date
    • Thread