use-livecode Digest, Vol 87, Issue 3
bobs at twft.com
Fri Dec 3 12:50:11 EST 2010
I knew that...
On Dec 3, 2010, at 7:30 AM, Robert Brenstein wrote:
> On 02.12.10 at 20:40 -0800 John Burtt apparently wrote:
>> Wouldn't more terms just add to the confusion.
>> Separate stacks are called "main" stacks.
>> The stacks that are part of (within) a main stack are called "sub" stacks.
>> Sub stacks that are separated from their main stack, become main stacks.
>> A main stack that has been turned into an application is an "executable".
>> Main stacks are savable.
>> Sub stacks are saved when their main stack is saved.
>> Executables are not savable.
>> And, sub stacks of the executable are not savable.
> Not quite...
> Stacks are really windows with objects and scripts.
> Stacks are saved in stackfiles.
> The mains (startup) stack in each stackfile is its mainstack.
> Other stacks in that stackfile are its substacks.
> When executable is produced, the runtime engine is merged with the stacks. However, depending on the settings, the mainstack and substacks are either kept together as in stackfile (neither can be modified at runtime) or substacks are split to become technically own mainstacks in own stackfiles (thus can be modified at runtime), although logically they remain part of the package.
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the Use-livecode