W3C home > Mailing lists > Public > public-xml-processing-model-wg@w3.org > February 2010

RE: Scoping of options and variables

From: <Toman_Vojtech@emc.com>
Date: Fri, 12 Feb 2010 03:25:17 -0500
Message-ID: <997C307BEB90984EBE935699389EC41CB12134@CORPUSMX70C.corp.emc.com>
To: <public-xml-processing-model-wg@w3.org>
> Does this text adequately cover the constraint?
>   The scope of option and variable names is determined by where they
>   declared. When an option is declared with p:option (or a variable
>   p:variable), unless otherwise specified, its scope consists of the
>   sibling elements that follow its declaration and the descendants of
>   those siblings. It is a static error (err:XS0004) if an option or
>   variable declaration duplicates the name of any other option or
>   variable in the same environment. That is, no option or variable may
>   lexically shadow another option or variable with the same name.
> I'm trying to be a little careful because a nested pipeline
> declaration could be a sibling element, but that's a different
> environment so it's not lexical shadowing.

I think so.

Received on Friday, 12 February 2010 08:25:59 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:32:48 UTC