• 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
Library loading policy on Mac OS X with Cocoa
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Library loading policy on Mac OS X with Cocoa


  • Subject: Library loading policy on Mac OS X with Cocoa
  • From: Stéphane Sudre <email@hidden>
  • Date: Tue, 26 Jun 2001 13:12:04 +0200

I have another stupid question.

I'm running Project Builder under gdb because I need to track a bug which makes it crash.

I just saw something surprising but not too much.

I added a ) without its counterpart and Project Builder beeped to warm me.

From gdb I can see that to generate the Beep, a shared library got loaded. This may explain why it's so slow to get the first beep on any Cocoa application. But why does Cocoa need to load a whole library at runtime just for NSBeep();

Couldn't it be done once for all at the System Launch, or the Application Launch ?


  • Follow-Ups:
    • Re: Library loading policy on Mac OS X with Cocoa
      • From: Eric Peyton <email@hidden>
  • Prev by Date: Re: Send action when textDidChange
  • Next by Date: Re: Send action when textDidChange
  • Previous by thread: Setting the Environment with AuthorizationExecuteWithPrivileges
  • Next by thread: Re: Library loading policy on Mac OS X with Cocoa
  • Index(es):
    • Date
    • Thread