Subject: Re: [xsl] Qualified variable names From: "Andrew Welch" <andrew.j.welch@xxxxxxxxx> Date: Mon, 10 Nov 2008 13:48:00 +0000 |
>> I might have missed the point, but weren't the "private" namespaces >> simulating Final behaviour? In other words, you used a private >> namespace to prevent certain variables etc being overridden? > > Well, I think those are two different properties you can combine. > You can have a public and final named template for instance: user > importing your stylesheet can use it, but not redefine it. Both > concepts are related as they refine the possible use of a component, > but in different ways. > > Of course, because private things cannot be accessed at all, then > cannot be redefined neither... Ahh I see - you would like visibility modifiers so users of the stylesheet library can't see the internal variable and template names... That would be good... I guess it would require something like a "visibility" attribute in addition to override="yes|no" -- Andrew Welch http://andrewjwelch.com Kernow: http://kernowforsaxon.sf.net/
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] Qualified variable names, Florent Georges | Thread | RE: [xsl] Qualified variable names, Michael Kay |
RE: [xsl] unparsed-text-collection(, Michael Kay | Date | Re: [xsl] Qualified variable names, Dimitre Novatchev |
Month |