Hi again,
At 06:12 PM 9/8/2005, you wrote:
> Yes, but I don't have to worry about a global variable changing and
> having a tested part of my encapsulated code no longer work. I have
> seen that happen many times when building my stylesheet, and can find
> nothing that changes this.
XSLT variables always have the same value once bound, people coming from
imperative programming languages sometimes expect that they should be
able to "change" the variable's value, which you can't do. You are the
first person I've seen that has complained that variables _do_ change
value. That never happens in XSLT.Some other problemmust be causing the
effect you see, if you posted a small example...
I too would like to see a demonstration of this.
In fact, I rather suspect that if Mike continues to provide us with small
but complete samples+stylesheets along with more of his quizzical,
hard-nosed questions, that all the mysteries of XSLT (all those mysteries
hidden in the archives of this list) will once again be brought forth into
the light.
Then we can go back to practicing our religion and not have to defend it so
much. :->
Cheers,
Wendell
======================================================================
Wendell Piez
mailto:wapiez(_at_)mulberrytech(_dot_)com
Mulberry Technologies, Inc. http://www.mulberrytech.com
17 West Jefferson Street Direct Phone: 301/315-9635
Suite 207 Phone: 301/315-9631
Rockville, MD 20850 Fax: 301/315-8285
----------------------------------------------------------------------
Mulberry Technologies: A Consultancy Specializing in SGML and XML
======================================================================
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--