I honestly don't understand your comment here.
What I was saying was, if I insert a template to solve one problem it
could change break other working aspects of the template, and I might
not realize until after I've paid the printer $10k to print something...
So saying that changing the template for Name changes the processing
at arbitrary points in the process, whenever <Name> appears is like
saying that if you change a C program and change the definition of a
function doname(..) then the processing changes whever the function
doname iis called, and without knowing where or if that function is
called, you don't know what effect changing the function will have. This
is all true, but it's not surprising, and not particular to xslt.
Your analogy does not mirror my point. Here's a better one. Assume a
working C program. Now I simply add function FooBar() into the source
code, and numerous other testing and debugged functions start returning
results that were different then they returned prior to my adding the
new function FooBar().
THAT is fragile.
-Mike
-----Original Message-----
From: David Carlisle [mailto:davidc(_at_)nag(_dot_)co(_dot_)uk]
Sent: Friday, September 09, 2005 4:54 AM
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: Re: [xsl] Apply-templates - how to omit top level element tags?
But the output changed from something I could publish to something
that would be very wrong to publish. And if that change was buried
deep in the output, well, OUCH because we might not catch it. That's
why I say XSL is fragile.
I honestly don't understand your comment here.
You clearly have a processing model in mind that makes this behavior
seem strange, but honestly I don't know what you find strange here.
When you are using push model (that is template matching) then
essentially you are executing the _document_ and each node in the
document fires code that is defined in a matching template.
So saying that changing the template for Name changes the processing at
arbitrary points in the process, whenever <Name> appears is like saying
that if you change a C program and change the definition of a function
doname(..) then the processing changes whever the function doname iis
called, and without knowing where or if that function is called, you
don't know what effect changing the function will have. This is all
true, but it's not surprising, and not particular to xslt.
David
________________________________________________________________________
This e-mail has been scanned for all viruses by Star. The service is
powered by MessageLabs. For more information on a proactive anti-virus
service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________
--~------------------------------------------------------------------
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>
--~--
--~------------------------------------------------------------------
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>
--~--