xsl-list
[Top] [All Lists]

Re: [xsl] Avoiding boneheaded mistakes in XSLT?

2010-12-30 09:58:58
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.

Jeff

On 12/30/10 10:10 AM, "J.Pietschmann" <j3322ptm(_at_)yahoo(_dot_)de> 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.

J.Pietschmann

--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: 
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--



--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--