On Wed, Feb 9, 2011 at 11:33 PM, Nonsanity wrote:
> get the number of chars in the SerialData of this stack
> repeat with a = 1 to it
> put char it & return after fld 1
> end repeat
>
>
get the number of chars in the SerialData of this stack
repeat with a = 1 to it
put char a of the Seria
On Wed, Feb 9, 2011 at 6:42 PM, Bob Sneidar wrote:
> I wonder why a lot of people think the threaded stack has to be sandboxed?
> The engine opened it, the engine knows how to communicate with it and other
> stacks. I really don't understand why a threaded stack would be inaccessible
> to other s
I wonder why a lot of people think the threaded stack has to be sandboxed? The
engine opened it, the engine knows how to communicate with it and other stacks.
I really don't understand why a threaded stack would be inaccessible to other
stacks. The only thing is that a threaded stack or perhaps
This is similar to what I was putting forward. I've thought more about it
more and have a sample scenario:
The user sees "Mainstack" with all the buttons and a progress bar, etc.
There is also a "Workhorse" stack that has all the heavy-duty processing
scripts, opened like so from the Mainstack:
[Sorry for the late reply - I've been very busy and only now found the time o
collect my thoughts on this interesting topic]
This thread has brought up various reasons for some form of multithreading and
several interesting ideas as to how this might be implemented. In the heat of
the discussio
