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

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

here's another one for you guys...

our Carbon app supports a CFM "plug-in" API, but all existing plug-in modules have been linked against InterfaceLib (i.e. - they're not Carbonized). obviously in OS X we can't load these plug-ins or our app will crash out. so the current workaround is that plug-ins are ONLY being loaded if we're not running on OS X. however, this limits our feature set on OS X because we will not EVER be able to load plug-in modules even after they become Carbonized w/o patching our application at some point down the road.

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...?

has anyone put together anything that can examine an independent code fragment at runtime and determine whether or not it has been Carbonized and thus can be loaded? is this even a possibility?

TIA. -phil.

---
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.


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.