This week's book giveaway is in the JDBC forum.
We're giving away four copies of Make it so: Java DB Connections & Transactions and have Marcho Behler on-line!
See this thread for details.
The moose likes Programmer Certification (SCJP/OCPJP) and the fly likes Console behaviour in Java Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Make it so: Java DB Connections & Transactions this week in the JDBC forum!
JavaRanch » Java Forums » Certification » Programmer Certification (SCJP/OCPJP)
Bookmark "Console behaviour in Java" Watch "Console behaviour in Java" New topic

Console behaviour in Java

Nick Widelec
Ranch Hand

Joined: Feb 28, 2013
Posts: 226

Directly from the official API:

Invoking close() on the objects returned by the reader() and the writer() will not close the underlying stream of those objects.

Why the object would not get close even invoking close()?

Thanks in advance.

Jeanne Boyarsky
author & internet detective

Joined: May 26, 2003
Posts: 32848

It looks like Java has a singleton reader. The following code returns true. This means that if the reader were closes, no other code could call it later.

[OCA 8 book] [Blog] [JavaRanch FAQ] [How To Ask Questions The Smart Way] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
I agree. Here's the link:
subject: Console behaviour in Java
It's not a secret anymore!