New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Random debugging information being printed #328
Comments
Hi @jonhare , Thanks for the excellent suggestion, it's high time the logging is rationalized indeed! Cheers |
+1 |
Hi @jonhare , I've started making logs less noisy + added a BRIDJ_QUIET=1 / -Dbridj.quiet=true switch to turn them off completely. Cheers |
(oh, and all logs now go through java.util.logging.Logger, so it should be possible to add file-based configuration and other regular logging magics / filters) |
Hi, There is a code in Demangler class which prints some info to stderr: if (totalArgs != parameterTypes.length) {
System.err.println("Not enough args for " + this);
return false;
} Is it possible to enhance it to support |
Closing now, please let me know if it needs to be reopened |
Both the native and java code contain a number of printf/println statements which were obviously designed for debugging. This is somewhat annoying when writing a command line program that uses Bridj as the output from Bridj gets mixed in with the output from the program.
It would be much better if Bridj used some kind of logging framework, or at least provided a way to turn off its output.
The text was updated successfully, but these errors were encountered: