W3C home > Mailing lists > Public > xproc-dev@w3.org > June 2011

Re: c:errors

From: Romain Deltour <rdeltour@gmail.com>
Date: Fri, 3 Jun 2011 17:43:39 +0200
Message-Id: <AF2AD444-7FAF-471C-8F43-1C4E15507072@gmail.com>
To: XProc Dev <xproc-dev@w3.org>
> in theory its possible, in actual practice I have not seen it

Yes I know. I'm looking for real life use cases, out of curiosity :)

Romain.

Le 3 juin 11 à 17:24, James Fuller a écrit :

> On Fri, Jun 3, 2011 at 5:08 PM, Romain Deltour <rdeltour@gmail.com>  
> wrote:
>> Hi all,
>>
>> The error document [1] appearing on the "error" input port of a  
>> p:catch is
>> basically a c:errors element with c:error children.
>>
>> In all the use cases I've met so fat it typically contains only one  
>> c:error
>> child. Are there existing use cases where it is contains either  
>> none or
>> several children ?
>>
>> I'd like to re-throw an error using p:error in a p:catch sub- 
>> pipeline, and
>> I'm trying to find the best approach when there are none/several  
>> c:error
>> children...
>
> c:errors is defined as follows;
>
> <c:errors>
>    c:error*
> </c:errors>
>
> so in theory its possible, in actual practice I have not seen it ...
> it remains to be seen if there are scenarios such as nested
> try/catches where multiple c:error children; maybe other impl have
> discovered such situations ?
>
> Jim Fuller
Received on Friday, 3 June 2011 15:44:14 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 3 June 2011 15:44:14 GMT