Summary: | Reduce use of System.out throughout the code. | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Maxime Daniel <maxime_daniel> |
Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> |
Status: | NEW --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | CC: | Olivier_Thomann |
Version: | 3.2 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Linux | ||
Whiteboard: |
Description
Maxime Daniel
2006-01-23 08:01:43 EST
Maxime, I believe this can be closed. There are 1164 references to System.out and 34 references to System.err in org.eclipse.jdt.core. I would consider that a good starting point would be to rationalize the tracing capabilities and to use explicit loggers for the parts of the source that may leverage 1.4, to home made loggers for the other parts (this is partly the case, but System.err still shows up in calls to Util.verbose). But I agree that this is a judgement call. The question must be something like: do we reduce the use of System.out and System.err to very few places that match precise criteria, or else do we consider that their use throughout the code is fine? Note: the use of explicit loggers in code conditionned by debug flags should be no big issue performance wise. We may want to avoid that elsewhere. Will move this to Philippe for decision. There is no usage besides the one in DEBUG mode. Will close post 3.7. |