Re: Must variables that contain maps be typed?

Norman Tovey-Walsh <[email protected]> Mon, 17 Aug 2020 16:02:02 +0100

Newsgroups	gmane.text.xml.saxon.help
Message-ID	<[email protected]>

Ihe Onwuka <[email protected]> writes:
> <xsl:variable name="actions" >
>       <xsl:map>
>             etc
>      </xsl:map>
> </xsl:variable>
>
> Doesn't seem right to me.

As I recall, if you initialize a variable with a sequence constructor
(content instead of a select attribute), then you are constructing a
tree unless you specify a type.

So, 

  <xsl:variable name="actions" select="map { … }"/>

would be fine, but to use xsl:map, you have to specify the type:

  <xsl:variable name="actions" as="map(*)">
       <xsl:map>
             etc
      </xsl:map>
  </xsl:variable>

You could argue that the processor ought to be able to tell that the
result is going to be a map, but keeping the rule simple means that
there’s no possible ambiguity if someone constructs something that could
be a map or could be a tree.

                                        Be seeing you,
                                          norm

--
Norman Tovey-Walsh <[email protected]>
https://nwalsh.com/

> There is hopeful symbolism in the fact that flags do not wave in a
> vacuum.--Arthur C. Clarke

_______________________________________________
saxon-help mailing list archived at http://saxon.markmail.org/
[email protected]
https://lists.sourceforge.net/lists/listinfo/saxon-help

signature.asc (application/pgp-signature, 832 B)