Re: Fodder for the @name proposal

/ Toman_Vojtech@emc.com was heard to say:
| Actually, I wonder if p:pipeline should have the 'type' attribute at
| all. It used to make sense when it was allowed to use p:pipeline for
| declaring pipelines in p:(pipeline-)library, but after it has been
| replaced by p:declare-step there, I don't see any real use for the
| 'type' attribute on p:pipeline any more. (Except when you want to refer
| to some of the pipeline's ports, of course, but then 'name' would do a
| better job, I think - and it would also be more consistent and
| intuitive.)

Well, you'd need the type if you wanted to make the pipeline recursive.

I think maybe it's an accidental oversight that p:pipeline isn't
allowed in p:library.

Given that p:import can import a p:pipeline, why can't you put several
p:pipeline's in a p:library?

Anyone disagree?

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | Reality is what refuses to go away when
http://nwalsh.com/            | I stop believing in it.--Philip K. Dick