I'm the one who started the thread, and it's the same for me - my program doesn't explicitly link against those libraries, but something somewhere obviously does. The first I knew about it was when a customer queried it, asserting that it was shortening his battery life on his laptop.
Seeing as this is the first query about it when the app has linked against these same libraries for the last 2 years at least, and been used by many thousands of people on their laptops, I thought it probably wasn't too big of an issue, but was curious as to the cause. From my empirical point of view, I judged that it didn't appear to be a significant enough issue to warrant me spending any more time digging into the causes and impacts. Gideon On 18/05/2010, at 7:28 PM, Keith Blount wrote: > ... > > Is this something I should be concerned about? As I'm not explicitly calling > anything that should do this, I'm assuming it's just a quirk of the system > caused by one of the frameworks I'm linking against, in which case I assume > there's not much I could do anyway. > _______________________________________________ Cocoa-dev mailing list ([email protected]) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
