Re: Multiple imports

/ Richard Tobin <richard@inf.ed.ac.uk> was heard to say:
| A simple solution would be to say that you don't import again from
| URLs that you've already imported from.  This wouldn't help libraries
| that refer to a local copy of another library, though.

So, given:

<p:pipeline-library ...>
   <p:import href="commonlib.xml"/>

  <p:pipeline name="pipeone">
    <p:import href="commonlib.xml"/>
    <p:import href="otherlib.xml"/>
    ...
  </p:pipeline>

  <p:pipeline name="pipetwo">
    <p:import href="otherlib.xml"/>
    ...
  </p:pipeline>

</p:pipeline>

The library loads commonlib.xml, so pipeone doesn't because it's
already "seen" it. However, pipeone does load otherlib.xml. And pipetwo
also loads otherlib.xml because it hasn't already been loaded in
the current scope.

Right?

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | The irrational is not necessarily
http://nwalsh.com/            | unreasonable.--Sir Lewis Namier