Re: [xsl] Managing debug logging in complex transforms: what do people do?

Subject: Re: [xsl] Managing debug logging in complex transforms: what do people do?
From: Alex Muir <alex.g.muir@xxxxxxxxx>
Date: Tue, 25 Mar 2014 09:26:07 +0000
On Tue, Mar 25, 2014 at 8:25 AM, George Cristian Bina
<george@xxxxxxxxxxxxx> wrote:
> Yes, optimizations in the XSLT processor like lazy evaluation may interfere
> with the debugging experience. Please at least make sure the "Optimization
> level" is set to 0 (zero) in the Saxon "Advanced options" dialog.

What effects does this have on the debugging experience for example?

Would that for example lead to stepping through the code with output
not being output in the right side window as expected at the time one
is moving through the code, and then all the output comes out at later
moment when it's a bit late to be of use really?

I've definitely use the debugger and with success often however
sometimes it's a pain.

I wonder without really thinking much into it if the controls and or
logic for debugging are borrowed from procedural languages and could
perhaps be quite different for xslt? ( no idea but what do you think?)

Thanks

-- 
-

Alex Muir
http://ca.linkedin.com/pub/alex-muir/36/ab7/125

Current Thread