Open
Conversation
|
To what extent would changing to Java 21 cause hardship for the user community, some of whom might be "stuck" on an older version of Java for reasons outside their control? I don't have an answer to this question. Personally, I think moving to Java 21 sounds fine, but I can appreciate how it might be problematic. |
This file contains hidden or 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
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.
I developed a tool to help analyze the call stack of a running program inside RARS at the Univerity of Applied Sciences Zwickau. The intent is that this tool may be used by others to help explain and understand the call stack.
Features
Screenshot
NOTE: I have used Java 21 and the rest of the code worked just fine. If this were a problem, I could rewrite the Callstack Analyzer to use Java 11 only. However, I would prefer to use Java 21 as this would involve quite a bit additional work.