Re: [xsl] Performance differences between xsl:for-each and xsl:template matches

["Dimitre Novatchev dnovatchev@xxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>]

To quote Donald Knuth: "Premature optimization is the root of all evil"
https://stackify.com/premature-optimization-evil/#:~:text=%E2%80%9CPremature%
20optimization%20is%20the%20root,is%20credited%20to%20Donald%20Knuth
.

I think he discovered a general law that is true for all overzealous
believers, as one can find ample proofs looking back in history.

Or, as they say: "The road to hell is paved with good intentions".


Thanks,
Dimitre


On Tue, Aug 16, 2022 at 10:11 AM Edward Porter edward.porter@xxxxxxx <
xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:

> I inherited an older stylesheet that makes extensive use of <xsl:for-each>
> matching elements (e.g., select=b//chapter[@eid]b) in the root template
to
> then call templates. Using Saxon, would there be any performance
> improvements if I refactored to use match templates and
> <xsl:apply-templates> as would generally be the best practice in this case?
>
>
>
> -Ed
>
>
>
>
>
> *Edward Porter*
>
> Doc Publishing Tech Lead | Documentation Engineering - DevOps
>
> Tel: + 1 919 531 2349
>
> SAS | 100 Campus Drive | Cary, NC 27513
>
>
>
> DID YOU KNOW?
> *SAS IS THE NO. 1 AI AND ADVANCED ANALYTICS SOFTWARE PLATFORM.
> <https://www.sas.com/gms/redirect.jsp?detail=GMS114829_158201>*
>
>
>
>
> XSL-List info and archive <http://www.mulberrytech.com/xsl/xsl-list>
> EasyUnsubscribe <http://lists.mulberrytech.com/unsub/xsl-list/782854> (by
> email <>)
>


--

[demime 1.01d removed an attachment of type image/gif which had a name of image001.gif]