Re: Library loading policy on Mac OS X with Cocoa
Re: Library loading policy on Mac OS X with Cocoa
- Subject: Re: Library loading policy on Mac OS X with Cocoa
- From: Rosyna <email@hidden>
- Date: Wed, 27 Jun 2001 02:30:13 -0700
Make me wonder why NSBeep isn't moved to some other library.
Ack, at 6/26/01, Eric Peyton said:
Because if it loaded it at application launch then *every*
application, including those that NEVER make a sound would incur
that startup/launch penalty. Everyone wants there apps to launch
faster, not slower, and in order to do this, less code needs to be
loaded at launch. To get less code loaded at launch some things are
loaded lazily (I believe that Appkit loads lots of frameworks
lazily, like QuickTime etc.). There is no need for your application
to load QuickTime just because it loaded AppKit, even though AppKit
does contain QuickTime code. (Loading something like QuickTime plus
all it's myriad parts would have a noticeable impact on every app
launch - you wouldn't want that now would you :-
--
Sincerely,
Rosyna Keller
Technical Support/Holy Knight/Always needs a hug
Unsanity: Unsane Tools for Insane People