On my IDE, mainstacks is currently 204. The stacks are stored in a linked list,
so no limit other than memory and performance.
Thanks,
Brian
On Aug 6, 2018, 7:14 AM -0500, Stephen MacLean via use-livecode
, wrote:
>
> > On Aug 6, 2018, at 8:05 AM, Paul Dupuis via use-livecode
> > wrote:
> >
>
> On Aug 6, 2018, at 8:05 AM, Paul Dupuis via use-livecode
> wrote:
>
> On 8/5/2018 11:29 PM, Stephen MacLean via use-livecode wrote:
>> @ Paul, they are different, based upon the type of build that needs to
>> happen for the source that is being looked at. The code has one handler name
>> th
On 8/5/2018 11:29 PM, Stephen MacLean via use-livecode wrote:
> @ Paul, they are different, based upon the type of build that needs to happen
> for the source that is being looked at. The code has one handler name that is
> the same (The init code in the builder), but after that the code is diffe
Hi Paul and Monte,
Thanks for the input!
@ Monte, I might be able to order the initial query so that they are grouped
together by builder type. Then I could process those together with doing one
load and unload for that group
@ Paul, they are different, based upon the type of build that needs
On 8/5/2018 8:51 PM, Stephen MacLean via use-livecode wrote:
> Any insight is appreciated!
>
I use a lot of library stacks, but our model is to load them on startup
and unload on shutdown (not really necessary singe the engine does this
on quit). Unless you have zillions of lines of code, I am not
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
> wrote:
>
> Hi All,
>
> I am currently using libr
