Re: [xsl] Profiling templates

[Wendell Piez <wapiez@xxxxxxxxxxxxxxxx>]

Hi,

At 09:50 AM 5/22/2008, Tony wrote:
> On Thu, May 22 2008 14:08:54 +0100, peter@xxxxxxxxxxxxx wrote:
> > I have a lot of data and some stylesheets which have /evolved/ over
> > time. I suspect that the quite a bit of the code is not ever being
> > executed, is there some way of finding the parts of the stylesheet that
> > is never accessed other than embeding xsl:message everywhere?
>
> AFAICT, the available XSLT profilers will at best tell you what
> templates have been used, not what templates haven't been used.  The
> ones that just report which templates have been used won't help you, for
> example, to work out which parts of a xsl:choose haven't been exercised.

This is the essence of it.

oXygen's profiler will show you which parts of the code are "hot", 
but you want to know which are cool, or rather, cold. Still, you 
might try oXygen. (1-month free licenses are available. Caveat: 
though I use oXygen happily, I haven't used this feature lately.)

Then there's the difference between parts of your code that are never 
used on sample data, and parts that can never be used due to logical 
reasons such as that the nodes being matched are never selected.

Cheers,
Wendell


======================================================================
Wendell Piez                            mailto:wapiez@xxxxxxxxxxxxxxxx
Mulberry Technologies, Inc.                http://www.mulberrytech.com
17 West Jefferson Street                    Direct Phone: 301/315-9635
Suite 207                                          Phone: 301/315-9631
Rockville, MD  20850                                 Fax: 301/315-8285
----------------------------------------------------------------------
  Mulberry Technologies: A Consultancy Specializing in SGML and XML
======================================================================