Re: Scope of step types

/ Norman Walsh <ndw@nwalsh.com> was heard to say:
| I think the only negative consequence of this decision is that two
| pipelines in a pipeline library that each import a different
| definition for a step type will cause an error where one is not,
| perhaps absolutely necessary. But we have namespaces to make such
| things unnecessary, right?

Oh, it also makes managing the set of step types visible to a pipeline
a little trickier.

If pipeline "a" imports pipeline "b" and pipeline "b" imports "c";
should "c" be available directly from within "a"?

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | Everything should be made as simple as
http://nwalsh.com/            | possible, but no simpler.