dcsimg
Login | Register   
RSS Feed
Download our iPhone app
TODAY'S HEADLINES  |   ARTICLE ARCHIVE  |   FORUMS  |   TIP BANK
Browse DevX
Sign up for e-mail newsletters from DevX

By submitting your information, you agree that devx.com may send you DevX offers via email, phone and text message, as well as email offers about other products and services that DevX believes may be of interest to you. DevX will process your information in accordance with the Quinstreet Privacy Policy.


Tip of the Day
Language: Java
Expertise: Intermediate
Apr 13, 1999

WEBINAR:

On-Demand

Application Security Testing: An Integral Part of DevOps


Redirect System.out and System.err

A crude but common way of debugging Java programs is to use the public System.out and/or System.err instances of PrintStream to display information:
 
System.out.println("Entering section A of my code");
One drawback to this method is that if the information is sent to a display (usually the default), it may scroll off the screen before you're able to view the message. Also, you may wish to have the messages stored in a more permanent way. You can accomplish this by redirecting the output to some place such as a printer or a local disk file using the System.setErr() and System.setOut() static methods. For example, this code will cause error messages to be stored in a disk file:
 
FileOutputStream fos = new FileOutputStream("errors.txt");
PrintStream ps = new PrintStream(fos);
System.setErr(ps);
You should note, however, that the PrintStream class is deprecated, and as a result, its use will trigger a deprecation warning when compiled.
Brett Spell
 
Comment and Contribute

 

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

 

Sitemap
Thanks for your registration, follow us on our social networks to keep up-to-date