Subject: RE: [xsl] manage errors and terminations, child thread of Re: [saxon] Too many attribute value templates? ++|
From: Owen Rees <owen.rees@xxxxxx>
Date: Fri, 25 Jan 2008 11:08:48 +0000
You seem to be looking for some kind of termination that "closes and tidies everything up" before dying. By that, I assume you mean that you want some kind of partial output to be available to the calling application? I wonder if you could explain this idea more clearly - are you thinking perhaps of some kind of model where everything on the call stack returns an empty sequence to its caller, bypassing all type checking, and then makes the half-written result tree available to the application? What would be the use case for this?
Clearly, one of the rules for xsl:message and error() is that order of execution is unpredictable, and therefore it's unpredictable how far execution has proceeded at the time of termination.
-- Owen Rees; speaking personally, and not on behalf of HP. ======================================================== Hewlett-Packard Limited. Registered No: 690597 England Registered Office: Cain Road, Bracknell, Berks RG12 1HN