Switch to Java Logging (java.util.logging)#110
Merged
JacobBarthelmeh merged 1 commit intowolfSSL:masterfrom May 7, 2025
Merged
Switch to Java Logging (java.util.logging)#110JacobBarthelmeh merged 1 commit intowolfSSL:masterfrom
java.util.logging)#110JacobBarthelmeh merged 1 commit intowolfSSL:masterfrom
Conversation
JacobBarthelmeh
approved these changes
May 7, 2025
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
3 participants
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.
This PR switches wolfcrypt-jni to use the Java Logging (
java.util.logging) framework instead of using plainSystem.out.println()statements.Using
System.out.println()is not ideal for performance nor memory usage, since Strings are always allocated even if debug logging is disabled. Using Java Logging, and switching debug calls to use lambda style defers String allocation/creation until the debug log is actually used/printed.