Menu
Why do we need to close a FileInputStream (and streams in general) in any case before we leave the program? What would happen otherwise? If the program stops before the input stream is closed explicitly in the program, doesn't the stream also close automatically?
427
yes you need to close stream because, the stream is already full with content and when you close the stream then you can use it again. also data is flush in drive when use flush method.
close() method closes this output stream and releases any system resources associated with this stream. The general contract of close is that it closes the output stream. A closed stream cannot perform output operations and cannot be reopened.
Yes you you should close it and you can close it if you pass it into a submethod. If you pass it into a Reader though, if you call close on the Reader it will also close the stream.
If it is not cleanly closed, then those resources may remain committed to the connection for an indeterminate time; details depend on the nature and configuration of the services involved.
File handles are scarce, finite resources. You can run out of them if you don't clean them up properly, just like database connections.
If you've written a small program with just one user you can get away with being sloppy and not closing in a finally block.
But if you end up using that idiom in an application that has many users and file handles you might have a problem.
"First we make our habits, then they make us." I try to apply best practices even when they aren't necessary.
155
Yes, when the process terminates the unmanaged resources will be released. For InputStreams this is fine. For OutputStreams, you could lose an buffered data, so you should at least flush the stream before exiting the program.
32
Dude. If you don't close your stream, your unit test will fail. Or at least, it should. So, that's why you need to close it. ;)
And while the OS will almost certainly clean up if you just exit, they'll generally get freed up faster if you explicitly close them. Furthermore, what if your code ends up in a long-running program sometime down the road? Then they'll have problems and curse you. :(
So, it's like washing your hands after using the bathroom. Eventually someone will pay the price if you don't do it. You can get away with it for a while, but it's still a good practice.
44
In addition to Jon's answer, it is generally a good idea to close any resource.
Think of a database connection. Your database cannot have infinite connections opened, in this case when you don't need it, it's better you close it as soon as you're done with it.
It is also good to make this a habit. "finally" block is your friend. In case of C++, you can also use RAII to manage this automatically.
37
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
