Re: NSBundle problem accumulates execution time
Re: NSBundle problem accumulates execution time
- Subject: Re: NSBundle problem accumulates execution time
- From: Michael Monscheuer <email@hidden>
- Date: Mon, 07 Feb 2005 11:45:47 +0100
Hi
>I am missing the beginning of the thread, but calling bundleForClass more then
>once for each dynamically loaded class will certainly ring my alarm bells.
>99% of the time this will be a sign of bad design decision.
Puh. So I managed to hit the 1% 8-)
Yes, you are right. Folks, the code snipped just shows the effect
and is not part of an application. The problem also occures if you load a
number of dynamic classes and call bundleForClass once for each.
The processing time of allFrameworks then depends on how many dynamic classes
that received a bundleForClass have been loaded.
Without invoking bundleForClass for each class the execution time of
allFrameworks is dramatically faster. I just did not expect this behaviour.
I expected allFramemworks' processing time being independent of the
number of previous bundleForClass calls.
MiMo
--
=======================================================
And refashioning the fashioned
lest it stiffen into iron
is work of endless vital activity.
[Goethe]
mailto:email@hidden
mailto:email@hidden
All about CALAMUS DTP suite:
http://www.calamus.net
=======================================================
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden