[x3d-public] Problems with XSLT maintenance issues?

[John Carlson]

Another possibility, but probably requires immutability is to translate
XSLT to Scala still using Saxon and perhaps MapForce, and then decompiling
your compiled Scala JVM byte code to Java.   I don’t know what the result
would be, but the result might be okay to maintain without expensive
tools.  One just needs an XSLT to Scala mapping in XSLT.  One can use the
mapping on itself.

The goal is to translate a declarative to functional to a very popular
language, Java, since Saxon is written in Java, Saxon continues to be used.

So what I think is needed is an XSLT to Scala/Saxon mapping.

I’m going to watch some Scala videos.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20231022/0728f685/attachment.html>