Improving JavaBean Coding

The first thing I have is to improve the coding of any JavaBean. We all know any java bean has members and lot of getters and setters. But for large number of member variables it becomes tedious to create the getters and the setters. The Java api can easily make it part of the jdk so that the getters and the setters are generated automatically. There can be a marker interface which any JavaBean class can implement and that will tell the compiler to generate the getter and setter code during compilation process. Of course, if you have any specialized getter or setter, that will override the system generated ones.

Optimizing Garbage Collection

My second idea is on garbage collection. Right now the JVM runs the garbage collection thread and automatically cleans up memory for objects whose reference count is zero. But some of these checks can be achieved during compile time. If some object is created within a method and it is assigned to local variable only during compilation, the compiler can automatically generate garbage collection code when the method exits. This will not happen if the object is returned or attached to some non-local variable. This will make the job of the garbage collector thread much easier and will result in a faster program.

One can even think of giving back the delete functionality optionally. This will result in less work for the compiler and definitely for the JVM. If the devloper is not sure if to use the delete functionality, he may leave it to the compiler or the JVM. For example, the developer did a mistake of calling delete on the same reference twice. This will result in MemoryAlreadyDeletedException (something like that) or plain old NullPointerException. Unlike in C++ world, developer can just take the delete out altogether, and the problem will disappear.

If you like this idea please send me email at gdind2003 .at. gmail. If you like you can also visit my web site at http://www.stock-article.com

Copyright