I am kind of doing multi-tasking using /core, but the way I am doing it is not
too pretty. It is a temporary solution until /Command comes out.
What I do is run multiple instances of REBOL. These instances can communicate
with each other using sockets. If you use windows, a batch file like so can
start your instances up without waiting for each to end:
-win 9x batch file---
start main.r
start slave.r
start slave.r
start slave.r
start slave.r
Advantages:
Poor mans multi-tasking
Get something working while waiting for /Command.
???
Disadvantages:
Must start processes ahead of time.
Waiting processes consume cpu cycles.
Having to use Sockets for inter process communication.
Requires OS dependent batch file.
Obviously will not work on non multi-tasking OS.
Security concerns!
Probably others...
I would first try to fake multi-tasking instead. Of course there is a some
things you cant do that with, since REBOL could be held up with the task.
--Ryan
[EMAIL PROTECTED] wrote:
> If you do the following...
>
> do %script.r
> do %script2.r
> do %script3.r
>
> The scripts will execute in succession, but when they complete is up to the
> processor, RAM, hard drive, etc.
>
> This is how I understand it, anyway, because you are essentially mult-
> tasking within a single task, which is the REBOL application itself.
>
> > Hi i'm writting to ask if it's
> > possible to launch other scripts
> > from a single script, but, without
> > having to wait for each script
> > to end before the next one can starts.
> >
> > thanks. timmy
> >
