Re: output binding error?

From: Norman Walsh <ndw@nwalsh.com>

James Garriss <james@garriss.org> writes:

> So we can't bind an input port in the declaration.  Can we bind one when we
> specify (use) it?  IOW, is this legal pipeline code?

Yes. In fact, *all* inputs must be bound when you *use* a step. If you
don't specify a primary input/output port, it'll get bound
automatically.

All *primary* output ports must also be bound (implicitly or
explicitly) when you use a step. Output ports that aren't primary can
be left unbound, in which case any data that flows throw them "falls
on the floor" (i.e. gets silently discarded).

Very helpful, thank you!

--J