Re: p:pipeline

/ Jeni Tennison <jeni@jenitennison.com> was heard to say:
| In standard programming languages, users tend to use naming
| conventions to distinguish between the functions that other users
| might want to reuse and those that are behind the scenes. I don't see
| why they can't do the same with a pipeline language.

They could. But some standard programming languages do allow you to do
better than that. Java, for example, allows inner classes, which is
the analogy that I guess I'm thinking of.

| At the end of the day, I think we want to have single files that hold
| multiple sibling invokable pipelines. We might have sub-pipelines as
| well (that are only usable within the pipeline in which they're
| declared), but if we do, we're only adding an extra feature that I
| don't think we really need in v1.0.

Yeah, I just noticed the "single files that hold multiple sibling
invokable pipelines" feature of a p:pipelines wrapper.

I don't want two ways of doing it. I don't want a p:pipelines wrapper
*and* nested p:pipeline elements, so if the "sibling invokable
pipelines" feature is really important, then I concede that
p:pipelines is the better choice.

                                        Be seeing you,
                                          norm

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