Re: [xsl] Lesson Learned: Don’t write XSLT programs this way

["Martin Honnen martin.honnen@xxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>]

Am 17.07.2022 um 15:13 schrieb Roger L Costello costello@xxxxxxxxx:
> For years my strategy in using XSLT to solve complex problems has been
this:
> Identify the series of transformations that must be performed on the input
data. Create an XSLT program that performs the first transformation. Conduct
tests to ensure the program works properly. Then create a second XSLT program
that takes the output of program#1 and performs the second transformation on
it. Conduct tests to ensure the combination of program#1 and program#2
produces the correct result. Then do the same for the third transformation.
And so forth.
> The result is a series of transformations applied to the input.


How did you run the series of transformations so far and how is that
different to using a shell to chain commands or transformations?

> When I read that I excitedly thought, bYes! That is the right way to build
applications! My, such folly in the way I been my implementing XSLT programs
all these years. The key to creating good XSLT programs -- and any program --
is to make each program do one thing well. Make each program a tool. Combine
tools using the command shell.b