Re: Runtime semantics of p:try

"Toman_Vojtech@emc.com" <Toman_Vojtech@emc.com> writes:
>
> Clearly, p:try may evaluate (parts of) both sub-pipelines.

Indeed. How's this?

   The output of a multi-container step is the output of exactly one
   of its subpipelines. In this sense, a multi-container step
   functions like a compound step. However, evaluating a
   multi-container step may involve evaluating, or partially
   evaluating, more than one of its subpipelines. It's possible for
   steps in a partially evaluated pipeline to have side effects that
   are visible outside the processor, even if the final output of the
   multi-container step is the result of some other subpipeline. For
   example, a web server might record that some interaction was
   performed, or a file on the local file system might have been
   modified.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | As the old hermit of Prague, that never
http://nwalsh.com/            | saw pen and ink, very wittily said to
                              | the niece of King Gorboduc, 'That that
                              | is, is'.-- Shakespeare