• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: AU, Obj-C and names
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: AU, Obj-C and names


  • Subject: Re: AU, Obj-C and names
  • From: Kyle Sluder <email@hidden>
  • Date: Fri, 2 Oct 2009 10:40:07 -0700

On Fri, Oct 2, 2009 at 4:00 AM, john smith <email@hidden> wrote:
> And yes, you're right, using a framework is not a solution I'm prepared to
> use. There's reasons why the library is static in the first place :-)

Be careful, there are ways this could fail in
spectacularly-hard-to-debug ways.  For example, if your plugins are
each linking against libwhatever, they might each define their own
SomeConstantString symbol which is used for KVO, options dictionaries,
or some other direct-pointer-comparison purpose.  This of course won't
work across the plugin boundary.

Also see QA1490 for other things to look out for when building static
ObjC libraries:
http://developer.apple.com/mac/library/qa/qa2006/qa1490.html

--Kyle Sluder
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >AU, Obj-C and names (From: john smith <email@hidden>)
 >Re: AU, Obj-C and names (From: Blue Cat Audio Dev <email@hidden>)
 >RE: AU, Obj-C and names (From: john smith <email@hidden>)

  • Prev by Date: Re: request for auval
  • Next by Date: RE: AU, Obj-C and names
  • Previous by thread: RE: AU, Obj-C and names
  • Next by thread: RE: AU, Obj-C and names
  • Index(es):
    • Date
    • Thread