[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: manage errors and terminations, child thread of Re
--On Friday, January 25, 2008 10:30:45 AM +0000 Michael Kay wrote:
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? Perhaps a 'throw' to a try/catch of some kind is what is intended. There was a discussion of 'try' at the beginning of this month which would be worth looking at for those who did not see it: <http://www.biglist.com/lists/xsl-list/archives/200801/msg00055.html> The idea of closing and tidying up makes me think of the kind of things I would put in a 'finally' in Java or an 'unwind-protect' in Lisp but those are all to do with undoing side-effects and carrying on. It is not clear what it would be for when there are no side effects, and especially if there is no sense of carrying on and doing something else. -- 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
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|