My main thought is if we are talking about loading and unloading thousands of times then script parsing may become costly. How costly I’m not sure… script parsing is pretty fast.
> On 6 Aug 2018, at 10:51 am, Stephen MacLean via use-livecode > <use-livecode@lists.runrev.com> wrote: > > Hi All, > > I am currently using library stacks that contain what I call custom builders, > that are livecode script libraries. These stacks have code for specific > instances and when done, I currently unload them. I like that I can use > these, and build them, on the fly, bringing that code in without having to > “disturb” the main app. > > As I’m about to start loading and unloading them hundreds if not thousands of > times, and very rapidly, I started thinking about how this would effect > performance, memory issues, etc. > > Does anyone have experience doing this and doing it rapidly? Anyone come > across any memory issues, leakage, etc.? Anything else I should look for in > doing this? Different ways to accomplish the same thing? > > Any insight is appreciated! > > Thanks, > > Steve MacLean > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
