Follow-up Comment #4, bug #25520 (project gnustep):
I think about the only case where this bug would actually be visible is when
sending a copyWithZone: or mutableCopyWithZone: message to a proxy (there
aren't many method signatures that look like that in the API).
And it occurs to me that, because those methods take an NSZone pointer
argument, they can't be used with objects in a different address space anyway
... so we should probably tell people not to call them unless they are sure
they aren't talking to a proxy to a remote object.
Or possibly we should also change the NSDistantObject class to catch those
two methods and convert them to -copy and -mutableCopy before sending them to
the remote process?
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?25520>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-gnustep mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-gnustep
