Re: [xsl] Avoiding boneheaded mistakes in XSLT?

Subject: Re: [xsl] Avoiding boneheaded mistakes in XSLT?
From: "Beck, Jeff (NIH/NLM/NCBI) [E]" <beck@xxxxxxxxxxxxxxxx>
Date: Thu, 30 Dec 2010 10:58:47 -0500
It seems like you could write a transform to do this for you.

Actually a transform that transforms your (transform in question) into a
transform that you run on  your instance.

Sort of a Transform-tron. Wrap it all up in a shell script or Xproc.

Sounds like a fun little project for a slow day at the end of the year or
someone with no New Years plans.


On 12/30/10 10:10 AM, "J.Pietschmann" <j3322ptm@xxxxxxxx> wrote:

>On 30.12.2010 10:05, Dave Pawson wrote:
>> Agreed, there are cases where this might be wanted as a response
>> from an xpath expression. Hence a warning. Hence 'not all the time'.
>I'd rather have a report of results of the various XPath expressions,
>including nontrivial sub expressions. Of course expressions which
>always resulted in an empty node set are of particular interest, but
>there are also expressions in filters and such. This gets near the
>"better debuggers" idea though: put the cursor in the IDE on an
>expression and get the value(s) (with context, if necessary) from
>the last run.

Current Thread