Subject: Re: [xsl] Do you run your XSLT code from a debugger? What debugger do you use? From: "Eliot Kimber eliot.kimber@xxxxxxxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> Date: Tue, 23 Aug 2022 15:00:49 -0000 |
Im with MartinI find the XSLT debugger in Oxygen to be less useful than for other languages. This may in part be because I do a lot of my work in DITA Open Toolkit which doesnt lend itself to easy debugging but I also get a lot of mileage out of using messages to see whats happening where. This is also true for my work with XQuery, whether in BaseX or MarkLogicI find it effective to just use messages to debug my code. Cheers, E. _____________________________________________ Eliot Kimber Sr Staff Content Engineer O: 512 554 9368 M: 512 554 9368 servicenow.com<https://www.servicenow.com> LinkedIn<https://www.linkedin.com/company/servicenow> | Twitter<https://twitter.com/servicenow> | YouTube<https://www.youtube.com/user/servicenowinc> | Facebook<https://www.facebook.com/servicenow> From: Martin Honnen martin.honnen@xxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> Date: Tuesday, August 23, 2022 at 9:34 AM To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx <xsl-list@xxxxxxxxxxxxxxxxxxxxxx> Subject: Re: [xsl] Do you run your XSLT code from a debugger? What debugger do you use? [External Email] Am 23.08.2022 um 16:10 schrieb Roger L Costello costello@xxxxxxxxx: > Do you run your XSLT code from a debugger? If so, what debugger do you use? > Sometimes I (need to/tend to) use the debugger in oXygen. But often, I try to find my way around with adding e.g. xsl:message or <debug><xsl:sequence select=".."/></debug>. Even now more than previously as I often run XSLT 3 through SaxonJS, where I don't know of a debugger.
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] Do you run your XSLT code, Elisa Beshero-Bondar | Thread | Re: [xsl] Do you run your XSLT code, Michael Kay mike@xxx |
Re: [xsl] Do you run your XSLT code, Elisa Beshero-Bondar | Date | Re: [xsl] Do you run your XSLT code, Michael Kay mike@xxx |
Month |