Re: System.err & System.out

[Nils Meier]

Hi Jeremias

> You sound as if using a System.out/err is a sacrilege. 

sorry, you're right - I should have checked the code
whether the System.err/out make sense where left.

Let me get back to you on that

Thanks
Nils

Re: System.err & System.out

[Jeremias Maerki]

You sound as if using a System.out/err is a sacrilege. Did you actually
look at the places where these calls are used? Last time this subject
was brought up I went through the whole codebase and did the cleaning up.
What remains are perfectly legal uses of System.out/err.

On 08.12.2005 03:27:39 Nils Meier wrote:
> Hi 
> 
> there's still places in the code where System.err and System.out is
> used but I assume they will replaced with logging calls eventually?
> 
> Thanks
> Nils
> 
> 
> System.err:
> CommandLineLogger.java
> TTFFile.java (2 matches)
> PreviewDialog.java
> RtfFile.java (3 matches)
> FileCompare.java (3 matches)
> SerializeHyphPattern.java (4 matches)



Jeremias Maerki

Re: System.err

[Jeremias Maerki]

This is done now. Some printStackTrace() calls are left mainly in the
Graphics2D implementations. That will be looked at when we move them to
Commons.

We'll have quite a pile of work before us to improve the whole exception
handling. But that's not for today.

Thanks for reminding us about fixing the console output, Nils.

On 14.11.2005 11:43:57 Jeremias Maerki wrote:
> FYI, I'm working on that.
> 
> The strategy is to remove stray System.out/err or
> Exception.printStackTrace() calls where possible, or pipe them to a logger
> instead. Some of those will need some additional work in the area of
> exception handling.
> 
> On 13.11.2005 23:37:17 Nils Meier wrote:
> > Hello
> > 
> > just wanted to bring your attention to the fact that
> > there's still quite a bit of System.err calls in
> > FOP code.
> > 
> > Is there a strategy for getting rid of those before
> > the release?
> > 
> > Thanks
> > Nils
> 
> 
> 
> Jeremias Maerki



Jeremias Maerki

Re: System.err

[Jeremias Maerki]

FYI, I'm working on that.

The strategy is to remove stray System.out/err or
Exception.printStackTrace() calls where possible, or pipe them to a logger
instead. Some of those will need some additional work in the area of
exception handling.

On 13.11.2005 23:37:17 Nils Meier wrote:
> Hello
> 
> just wanted to bring your attention to the fact that
> there's still quite a bit of System.err calls in
> FOP code.
> 
> Is there a strategy for getting rid of those before
> the release?
> 
> Thanks
> Nils



Jeremias Maerki