Use XSLT3 for stylesheets #4338
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks, @chrispy-snps . This is backwards compatible and there seems to be no reason not to do it. Many of the |
chrispy-snps
force-pushed
the
feature/use-xslt3
branch
from
add9a0d
to
d441e51
Compare
|
@stefan-jung - agreed! This will be an exciting step forward in code expressiveness. When the time comes to actually use some features, I can run the refactoring operation in #4123 to make some code updates programmatically. |
jelovirt
added
priority/medium
Signed-off-by: chrispy <chrispy@synopsys.com> Signed-off-by: Jarno Elovirta <jarno@elovirta.com>
jelovirt
force-pushed
the
feature/use-xslt3
branch
from
d441e51
to
6fd9d77
Compare
jelovirt
approved these changes
Dec 10, 2023
robander
approved these changes
Dec 11, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Changes XSLT style templates from version 1.0 and 2.0 to version 3.0.
There are no changes to the actual code; only the stylesheet headers.
Motivation and Context
This is a pipecleaner change to flush out any external or third-party incompatibilities that might result from switching to XSLT3. Because there are no code changes, the version change is easily reversed to troubleshoot or work around issues.
How Has This Been Tested?
Automated tests pass. Manual testing with old plug-ins.
Type of Changes
Documentation and Compatibility
This doesn't require end-users or plug-in developers to change anything. However, the release notes could link to https://www.w3.org/TR/xslt-30/#incompatibilities.