On Thu, Apr 2, 2009 at 11:06 PM, Ryan Joseph
<thealchemistgu...@gmail.com> wrote:
>
> On Apr 3, 2009, at 9:59 AM, Mark Ritchie wrote:
>
>> On 2-Apr-09, at 10:38 PM, Ryan Joseph wrote:
>>>
>>> I think I need explain what exactly I need this for. I'm making a Pascal
>>> bridge to Cocoa and it would be convenient if I could pass a CF type or a
>>> Pascal wrapper indiscriminately and decide at runtime how they should
>>> handled. If I knew the type was CF (thus NOT a wrapper, because it was
>>> created from a CoreFoundation function) I would not dereference the object
>>> and cause crashing.
>>
>> Hi Ryan
>>
>> Would the Pascal wrapper be a custom subclass of NSArray which has some
>> specific functionality for the bridge? I'm trying to understand how this
>> wrapped array would be different from another array. As Ali said, it would
>> be better if you could avoid the test.
>
> The wrapper is simply a Pascal object that encapsulates a Cocoa object. The
> underlying object is exactly the same as it appears in Cocoa, except it's
> accessed via Objective-C runtime functions. The fact it's a "wrapper" is
> really not important, I will be testing a CF type or the underlying Cocoa
> object.
>
> I'm prepared to abandon this if it's going to dangerous, it would just be
> nice if users didn't have to choose manually. Thanks.
I'm not sure what you mean by a "wrapper" here. Is this just a custom
Objective-C class? If so, then you can just test using Objective-C
introspection methods, like -isKindOfClass:
if([array isKindOfClass:[YourPascalWrapperClass class]])
...it's your wrapper...
else
...don't do anything funny...
Mike
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
