Re: q on xpath 2.0 reserved functions

[Ramkumar Menon <ramkumar.menon@gmail.com>]

I guess the following section answers this.

"A subtraction operator must be preceded by whitespace if it could
otherwise be interpreted as part of the previous token. For example,
a-b will be interpreted as a name, but a - b and a -b will be
interpreted as arithmetic expressions. (See A.2.4 Whitespace Rules for
further details on whitespace handling.)"



On Sat, Jun 20, 2009 at 12:44 AM, Ramkumar
Menon<ramkumar.menon@gmail.com> wrote:
> Spec lists the following as reserved fn names.
>
> attribute,comment,document-node,element,empty-sequence,if,item,node,processing-instruction,schema-attribute,schema-element,text,typeswitch
>
> Does this mean that user can register other "unprefixed" xpath
> functions [custom ones].
>
> If No, okay.
> If yes, quick, but naive Q.
> What if user defined an unprefixed function named instruction(), or a
> function named sequence()?
> Lets say instruction() and sequence() functions return numerical values.
> What would happen if the user performed the xpath on the following doc.
>
> <numberOfTasks>
>   <processing>20</processing>
>   ...
>    <empty>1</empty>
> </numberOfTasks>
>
> xslt
> -------
> <xsl:template match="numberOfTasks">
>    <netValue><xsl:value-of select="processing-instruction()"/></netValue>
>    <someValue><xsl:value-of select="empty-sequence()"/></someValue>
> </xsl:template>
> Whats the behaviour?
> Should this be explicitly disallowed?
>
> I'll close my eyes and wait :-) Someone's gonna use a sledgehammer on me :-)
>
> Ram
>



-- 
Shift to the left, shift to the right!
Pop up, push down, byte, byte, byte!

-Ramkumar Menon
 A typical Macroprocessor