Subject: RE: [xsl] Confusing trace from Saxon HE9 From: "Michael Kay" <mike@xxxxxxxxxxxx> Date: Wed, 9 Dec 2009 10:26:11 -0000 |
> I will look into the possibility of declaring types for > parameters throughout my code. In this particular instance, > the $node parameter could be really any element from the > source document (but not a sequence) Then describe it using as="element()". That's quite sufficient to catch this error early on, and it also shares your knowledge of what the variable is supposed to contain with the people reading and debugging your code, as well as sharing it with the compiler, which can make use of the knowledge when optimizing. Regards, Michael Kay http://www.saxonica.com/ http://twitter.com/michaelhkay
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] Confusing trace from Saxo, Jeroen Hellingman | Thread | [xsl] XSLT 2.0 grouping and text no, Kenneth Reid Beesley |
Re: [xsl] Confusing trace from Saxo, Jeroen Hellingman | Date | Re: [xsl] What short short XSLT 2.0, Tony Graham |
Month |