> On Feb 21, 2016, at 1:14 PM, David Hoerl <[email protected]> wrote: > > I have a rather large framework that does something very specific, many (or > most) users will have no interest in using it. What I'd like to do is not > have to statically link it into my app, either via a static library or a > dynamic one that always loads at launch.
If the framework is properly written it will do pretty much nothing at load time. The only overhead of loading it will be from the dynamic library loader (dyld) mapping the file and resolving its symbols, which is probably minimal. As with a lot of other optimizations, it’s best to actually measure what the overhead is, before putting energy into trying to reduce it. —Jens
_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to [email protected]
