This page is no longer maintained — Please continue to the home page at www.scala-lang.org

java 7?

3 replies
Tim P
Joined: 2011-07-28,
User offline. Last seen 1 year 4 weeks ago.

Hi
Is there any recommendation about whether or not we should use Java 7
with 2.9.0.1?
Tim

ewilligers
Joined: 2008-08-20,
User offline. Last seen 3 years 17 weeks ago.
Re: java 7?

They are working together for me. I wouldn't put Java 7 in production
yet due to the issues reported by http://lucene.apache.org/

On Aug 12, 5:58 am, Tim P wrote:
> Hi
> Is there any recommendation about whether or not we should use Java 7
> with 2.9.0.1?
> Tim

Tobias Neef
Joined: 2010-08-13,
User offline. Last seen 42 years 45 weeks ago.
Re: java 7?

Come on. Even though we are a scala focused group of people here we
shouldn't be biased. As with every new release of software, people
should be testing it extensively before using it in production. So
this is also true for java 7 and a good reason for a lot of people to
not use it in production (for now). The bug which was reported by the
lucene guys was tracked down and can be avoided by adding some
parameters when starting you JVM. The bug was also there in former
versions but wasn't that big of an issue because it was not the
default setting.

Coming to you question Tim. I see no reason not to use scala in
combination with java 7 from a compatibility aspect. As usual java 7
only added stuff and the bytecode and the libs are compatible to
previous versions.

On Aug 12, 2:47 am, Eric Willigers wrote:
> They are working together for me.  I wouldn't put Java 7 in production
> yet due to the issues reported by  http://lucene.apache.org/
>
> On Aug 12, 5:58 am, Tim P wrote:
>
>
>
>
>
>
>
> > Hi
> > Is there any recommendation about whether or not we should use Java 7
> > with 2.9.0.1?
> > Tim

adriaanm
Joined: 2010-02-08,
User offline. Last seen 31 weeks 4 days ago.
Re: Re: java 7?
one concern with moving to Java 7 is that some classes in the JDK that before didn't take type parameters now do (e.g., in the Swing library), so you'll have to supply arguments when they can't be inferred (e.g., when extending such a class)
once you've added these type arguments, you can't go back to Java 6, since the compiler will complain you're applying type arguments to classes that don't have type parameters
to allow targeting both Java 6&7 with the same Scala codebase, we're considering an @uncheckedTypeApply annotation (the compiler would silently drop type arguments when they're applied to a type that does not expect any -- if the type application as a whole is annotated as unchecked)
cheers,adriaan

Copyright © 2012 École Polytechnique Fédérale de Lausanne (EPFL), Lausanne, Switzerland