| |||
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
Dear Peter,
DO works VERY hard to keep everything thread safe (even object double pointers get dereferenced). This is the reason for the NSDistantObjects you are getting. Now there are situations where you can guarantee that an object will not be accessed by multiple threads, and you don't want the overhead of using the 'bycopy' keyword. The hack I have found to this is the following set of calls, making use of casting so that the DO system does not know an object is involved. I have no idea if this will survive various upgrades, but it works on both OS X 10.0.4 and GNUStep under Linux without any problems (just a compiler warning). If anyone out there knows of a better method, I'd love to hear it.
| References: | |
| >Re: Distributed Objects help - a fun hack (From: Miguel Morales <email@hidden>) |
| Home | Archives | FAQ | Terms/Conditions | Contact | RSS | Lists | About |
Visit the Apple Store online or at retail locations.
1-800-MY-APPLE
Contact Apple | Terms of Use | Privacy Policy
Copyright © 2007 Apple Inc. All rights reserved.