Re: AspectJ: solution to Java's repetitiveness?
"jhc0033@gmail.com" <jhc0033@gmail.com> writes:
All of these operations follow a very simple pattern that can be
easily formalized. However, Java programmers have to implement each of
these methods by hand for every class. Another common example is the
trivial getters and setters.
If they follow a pattern, it can be put in a utility class and
be delegated to.
Getters and setters are questionable, because they break
encapsulation, and getters break "tell, don't ask".
Bar b = new Bar(x, y);
Why not
b = new Bar(x, y);
This would make such lines shorter, but add complexity to
the language, because there would be additional rules needed.
Programmers already can use Common Lisp and its macros to
get rid of all such repetitivness. When one uses Java, one
/has decided against this/. Then why complain? Why decide
to use a verbose language, then complain about its verbosity?
(For Lisp programmers reading this, I'm basically thinking of
defmacro)
If someone wants Lisp, he can use Lisp. We could modify Java
until it has become Lisp, but there is no need to do so,
because Lisp already exists. There even are Lisp and Scheme
implementations for the JVM.