Skip to main content

Rémi Forax

Rémi Forax is Maitre de Conférence at University of Marne-la-Vallée since 2003 where he obtained his PhD on multi-method in Java. He has been using Java for many years and enjoys himself hacking the JDK.


forax's blog

Property and interceptors

Posted by forax on January 11, 2007 at 8:10 AM PST

Since my last post,

Cay Horstmann

has recalled that properties are intended for tools

Hans Muller
bid up
by saying that property syntax is useless
without a way to define bound properties.

Property and bean spec

Posted by forax on January 8, 2007 at 2:20 PM PST

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.

All your property are belong to us

Posted by forax on January 5, 2007 at 8:01 AM PST

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 ?

Call me Santa

Posted by forax on December 17, 2006 at 7:11 AM PST

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

Type inference of local variables

Posted by forax on December 11, 2006 at 2:56 AM PST

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

  foo=new Foo();

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

java.lang.Unreachable as type argument

Posted by forax on November 21, 2006 at 2:13 AM PST

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 :

How far is fidji - Reloaded

Posted by forax on November 15, 2006 at 6:24 AM PST

This blog is an infrared echo to Matthias Ernst's last post
titled "How far is fidji".

Stupid question: Why the creation of array of parametrized type is unsafe ?

Posted by forax on November 9, 2006 at 2:19 AM PST

I don't understand why array creation of array of parametrized
type is forbidden by the JLS.

Let me take an example :

Reified generics in Java

Posted by forax on November 6, 2006 at 2:23 AM PST

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

JSR 277 and ahead of time compilation

Posted by forax on October 19, 2006 at 7:27 AM PDT

Last week, an early draft of Java Module System (JSR277)
was published.