Factor folks -
I'm missing something trying to properly set up the components
of a sequence to be passed to run-pipeline. I intend the components
to be:
(1) a process launch descriptor, with stack effect ( -- desc ) ;
(2) a quotation composed only of run-detached, stack effect ( desc --
process ) ;
(3) a quotation to store the proc in a variable, stack effect ( process --
);
-these followed by quotations of words with stack effect ( -- ),
all duly wrapped in a sequence { … }.
The word description for run-pipeline says that run-pipeline:
"Creates a pipe between each pipeline component, with the output of each
component becoming the input of the next.
The first component reads input from input-stream and the last component
writes output to output-stream.
Each component runs in its own thread, and the word returns when all
components finish executing. Each component outputs a result value."
My sundry attempts to meet these requirements typically result in a
data stack underflow on execution, or an aberrant stack effect during
compile.
Can anyone sketch a proper set-up for generic requirements like mine,
to successfully pass a component sequence to run-pipeline?
Thanks for any suggestions,
~cw
--
*~ Memento Amori*
------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________
Factor-talk mailing list
Factor-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/factor-talk
