Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xsl] Qualified variable names

From: "Dimitre Novatchev" <dnovatchev@--------->
To:
Date: 11/3/2008 5:57:00 PM
> If it's a global variable in a module intended for reuse, I would say
> that you should certainly do this.

On the other side, using global variables (extensively) may not
probably be a best practice in any programming language and especially
so in a functional programming language.


-- 
Cheers,
Dimitre Novatchev
---------------------------------------
Truly great madness cannot be achieved without significant intelligence.
---------------------------------------
To invent, you need a good imagination and a pile of junk
-------------------------------------
Never fight an inanimate object
-------------------------------------
You've achieved success in your field when you don't know whether what
you're doing is work or play



On Mon, Nov 3, 2008 at 10:24 AM, Colin Paul Adams
<colin@xxxxxxxxxxxxxxxxxx> wrote:
>>>>>> "JamesXslt" == JamesXslt Smith <jamesxsltsmith@xxxxxxxxx> writes:
>
>    JamesXslt> Hi, Wondering if qualifying variable names in XSLT 2.0
>    JamesXslt> is a good idea as in:
>
>    JamesXslt> <xsl:variable name="a:x">...</xsl:variable>
>
>    JamesXslt> where the prefix a is bound to a namespace URI.
>
> If it's a global variable in a module intended for reuse, I would say
> that you should certainly do this.
> --
> Colin Adams
> Preston Lancashire


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent