Notes on implementing concise calls to constructors with type parameters
howard.lovatt at iee.org
Thu May 14 20:35:53 PDT 2009
A source statement would be great at dealing with this problem - pity
source hasn't made it into 7 then we could fix this problem in 8.
Rémi Forax wrote:
>Alex Buckley a écrit :
>> Rémi Forax wrote:
>>> Re-read section 4.8 of the JLS :)
>>> *"It is possible that future versions of the Java programming
>>> language will disallow the use of raw types."
>>> So it's seems that someone, one day conceive that.
>> Is it conceivable to drop raw types and hence migration compatibility?
>> Sure. Is it an upgrade in behavior? Let's ask people still on 1.4
>> who use raw types. They may have something to say about the increased
>> costs you'd impose on them when they try to upgrade their codebase.
>First we talk about source compatibility, not binary one.
>Second, there is no migration compat problem if javac can read source in
>1.4 and compile them to 1.7.
>and not stupidly require source 1.5 if target is 1.5, but you already
>So if there is a raw type the compiler can suggest that source should be
>compiled with -source 1.6
>Third, Are you one of the guys that decide that if you want to use module
>you need to change the layout of the directories of the sources ?
>Backward compatibility is the main goal, if it doesn't narrow the future.
>But I agree with you that this is not a small change, so not for 1.7.
More information about the coin-dev