Great! That answers it, Jameson. Thanks!
On Thu, Jul 17, 2014 at 8:48 PM, Jameson Nash <[email protected]> wrote: > you can also call `spawn` (or `open`) rather than `run` to run a process > asynchronously in the current task (it returns a process handle rather than > a return value): > > > function run(cmds::AbstractCmd, args...) > > ps = spawn(cmds, spawn_opts_inherit(args...)...) > > success(ps) ? nothing : pipeline_error(ps) > > end > > > On Thu, Jul 17, 2014 at 8:33 PM, Elliot Saba <[email protected]> > wrote: > >> Thanks, I'll take a look, although I have the gut feeling that these >> functions are targeted toward multiple processes. >> -E >> >> >> On Thu, Jul 17, 2014 at 4:49 PM, Tim Holy <[email protected]> wrote: >> >>> Check out the implementation of multi.jl:pmap (the part in the @sync and >>> @async blocks), it's a great example. >>> >>> --Tim >>> >>> On Thursday, July 17, 2014 04:23:48 PM Elliot Saba wrote: >>> > I was reading the docs >>> > < >>> http://julia.readthedocs.org/en/latest/manual/control-flow/#tasks-and-event >>> > s>, and it seems to me that it's saying I can use tasks to run multiple >>> > subprocesses at once. E.g., if I have some long-running subprocesses >>> such >>> > as `sleep 10`, I should be able to wrap each in a Task and use the >>> inherent >>> > wait() command that running each subprocess would entail to switch to >>> > another task and kick off another subprocess. Is this correct? If it >>> is, >>> > can someone provide me a quick example? I can't seem to get this to >>> work, >>> > but I've never used Tasks before so that's hardly surprising. ;) >>> > -E >>> >>> >> >
