Lol I was thinking in the same direction.
You could make a stylesheet were you put in your common misstakes to
check the stylesheet you are working on at the moment. These would be
like tests on node iso node() etc (like in some other programming
languages a = 1 iso a== 1).
On Thu, Dec 30, 2010 at 8:04 AM, Andriy Gerasika
<andriy(_dot_)gerasika(_at_)gmail(_dot_)com> wrote:
On 12/29/2010 12:35 AM, David Sewell wrote:
1. In an XPath expression, using "something/node" where I wanted
"something/node()" [ditto text vs. text()]: always means zero results and
can drive you crazy if you don't notice the missing parentheses;
IDE should highlight functions inside XPath, for example in bold
right now, Eclipse for example does not, and it supports XPath 1.0 only
Has anyone come up with a useful list of "things to check any time my
code is not working the way it should"?
FindBugs.xslt checking XSLT would help, something similar to already
existing FindBugs in Java world
--~------------------------------------------------------------------
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>
--~--