Re: default pipeline input

/ ht@inf.ed.ac.uk (Henry S. Thompson) was heard to say:
| But I think on reflection that we should default to the _first_
| of the pipeline's declared inputs even if there are more than one.
| Reason being that I'm pretty sure most implementations will map stdin
| to the first declared input, and it will confuse users if that default
| doesn't carry through inside, as it were.

I don't have any plans to implement stdin that way, but nevermind :-)

I could live with that story.

| Or does this bring us back to the question of defaulting the primary
| input declaration for all containers, which we discussed a while ago
| and stalled on. . .?

I thought the solution we came up with subsumed the discussion.

For every case except the very beginning of a p:pipeline, there will
be a preceding step which either provides a default readable port or
there isn't a default readable port.

Any unbound input on a step is bound to the default readable port.

Some rule that establishes the default readable port in the p:pipeline
gives us complete coverage, I think.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh
XML Standards Architect
Sun Microsystems, Inc.