Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: detecting "bad" code fragments in OS X...

We take the same approach. Non-Carbon plugins just won't load under X as
InterfaceLib is not available. Under 9, non-Carbon plugins will load and
work fine (handy for where we support legacy hardware that does not have X
drivers).

Cheers,

Steve.

--
Stephen Baxter
Development Manager
Improvision
email@hidden
Tel:+44-2476-692229
Fax:+44-2476-690091

------------------------------------------------------
Volocity - New Dimensions in High Performance Imaging

http://www.improvision.com/products/Volocity
------------------------------------------------------


> From: "Phillip A. Kavan" <email@hidden>
> Date: Thu, 28 Feb 2002 08:14:33 -0600
> To: email@hidden
> Subject: Re: detecting "bad" code fragments in OS X...
>
> thanks Bryan and Jim...
>
> these are both acceptable solutions...i was just wondering how other
> developers were handling this.
>
> thanks! -phil.
>
> On Thursday, February 28, 2002, at 07:57 AM, Jim Correia wrote:
>
>> On Thursday, February 28, 2002, at 02:26 AM, Bryan Pietrzak wrote:
>>
>>> Can you just have the plug-in developers changed the creator or file
>>> type of the plug-in? Or add an empty resource to indicate carbon
>>> compatibility?
>>
>> BBEdit did something similar with its plug-in API (a fragment naming
>> convention) since we support multi-fragment CFM plug-ins in which you
>> can build the classic version and the carbon version into the same
>> binary.
>>
>>> On Thursday, February 28, 2002, at 12:32 AM, Phillip A. Kavan wrote:
>>>
>>>> i would like to add a feature on OS X to detect plug-in modules that
>>>> cannot be used with our app in OS X; in other words, have the
>>>> application detect whether or not a plug-in module has been linked
>>>> against InterfaceLib at runtime or something like that and then
>>>> choose not to load it. however, since the Carbonized version of our
>>>> app is not linked against InterfaceLib, i don't think i can just
>>>> check for an InterfaceLib function == "unresolved code fragment
>>>> symbol" in OS X...?
>>
>> You *should* be able to just try opening a connection to the plug-in.
>> If CFM can't close because InterfaceLib isn't present, you'll get an
>> error, and you know you can't load the plug-in. Is this an unacceptable
>> solution?
>> _______________________________________________
>> carbon-development mailing list | email@hidden
>> Help/Unsubscribe/Archives:
>> http://www.lists.apple.com/mailman/listinfo/carbon-development
>> Do not post admin requests to the list. They will be ignored.
>>
>>
> ---
> Phillip A. Kavan <mailto:email@hidden>
> _______________________________________________
> carbon-development mailing list | email@hidden
> Help/Unsubscribe/Archives:
> http://www.lists.apple.com/mailman/listinfo/carbon-development
> Do not post admin requests to the list. They will be ignored.
_______________________________________________
carbon-development mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/carbon-development
Do not post admin requests to the list. They will be ignored.
References: 
 >Re: detecting "bad" code fragments in OS X... (From: "Phillip A. Kavan" <email@hidden>)



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.