Article:  |
What I Hate About Your Programming Language | |
| Subject: | Java; I want a destructor! | |
| Date: | 2003-05-18 18:20:29 | |
| From: | anonymous2 | |
|
Response to: Java; I want a destructor!
|
||
| The purpose of a destructor is to free resources (not just heap memory). Closing files, sockets, database connections, etc., even in the presence of exceptions, without having to remember to try-finally-release them can be quite powerful. Garbage collection is nice and has its place, but isn't a panacea. | ||
Showing messages 1 through 1 of 1.
-
Java; I want a destructor!
2003-05-19 03:26:12 anonymous2 [View]
This is especially true in a object-oriented language. I have a stream. Is it a memory stream or does it represent a file, a socket, or something else that the garbage collector won't release (or that a finalize method will release too late)? If you don't know, then you'll have to remember to try-finally-close that stream. Even when dealing with memory streams. That's convenience?
