Among the questions about my
property proposal and its implementation.
One can be answered easily.
Why don't provide property change support ?
Because there are several ways to implement a property change support
depending on what you want.
Happy new year everyone.
Since my last post, i've done some homeworks :),
and i'm please to present you a new version of the
prototype java compiler which includes property support.
First, why properties ?, we have already fields and any IDE
have a menu item that can generate getters and setters, so why do,
we need properties ?
Since my last post, i've played with javac enought to be able to provide a patch that enables to let the compiler infers the type of local variables.
Life is a matter of choices
For an average duke, the big difference between a language like
PHP, Python and Java is that you have to declare the type
of the variables.
In general, it's not a big beal for a statement
like this one
to declare the type and so write it like that
Foo foo=new Foo();
The advantage of declaring the type Foo is that
the compiler won
The closure proposal specifies a new type java.lang.Undeclarable
that can be used as a return type of a method
to indicates that this method never returns.
All instructions after a call to a method that returns Undeclarable
is unreachable, by example :
This blog is an infrared echo to Matthias Ernst's last post
titled "How far is fidji".
I don't understand why array creation of array of parametrized
type is forbidden by the JLS.
Let me take an example :
Neal Gafter post a blog entry
about adding reified generics to Java.
I likethat proposal mostly because
developpers will have the choice betweeen reified or not reified
Last week, an early draft of Java Module System (JSR277)