- About Scala
- Documentation
- Code Examples
- Software
- Scala Developers
[Eclipse Scala plugin] Compiler bug?
Thu, 2010-04-15, 23:34
It seems that the compiler generates lots of new warnings and even some
errors on Scala code that compiled without warnings until now.
Method parameter names that are the same as other identifiers in the scope
of the class containing the method seem to be causing a lot of these.
I have a piece of code like
val style = new StyleContainer
{
def apply(style : String) { /*... */ }
}
which may be a bit crummy but used to compile fine before. The compiler now
complains that "recursive value style needs type".
When I compile the code using my Ant Scala build task there is no complaint
but the compiler in Eclipse insists I rename the parameter to apply.
Is this intended behaviour or is it a compiler bug?
Gr. Silvio
Fri, 2010-04-16, 07:37
#2
Re: [Eclipse Scala plugin] Compiler bug?
Hello Paul,
I just checked, Strict warnings is not checked...
I do get some actual errors here and there (about 40 warnings and 3/4 errors
on ~200 source files).
Gr. Silvio
Fri, 2010-04-16, 08:17
#3
Re: [Eclipse Scala plugin] Compiler bug?
On Fri, Apr 16, 2010 at 7:27 AM, Silvio Bierman
wrote:
> I do get some actual errors here and there (about 40 warnings and 3/4 errors
> on ~200 source files).
Are these errors shown in the "Problems View", in the editor or both?
Best,
Ismael
Fri, 2010-04-16, 08:37
#4
Re: [Eclipse Scala plugin] Compiler bug?
Ismael Juma wrote:
>
>
> Are these errors shown in the "Problems View", in the editor or both?
>
>
Both. Initially I also thought it was a reappearance of the old editor
warnings bug but this one turns up in the problems view as well. Therefore I
expected it to come up via the Ant build also (I use the same distribution
version as the plugin version) but that build went without errors.
Gr. Silvio
On Thu, Apr 15, 2010 at 03:34:45PM -0700, Silvio Bierman wrote:
> It seems that the compiler generates lots of new warnings and even
> some errors on Scala code that compiled without warnings until now.
Are they warnings about shadowing? It has come up a good half a dozen
times so far today that apparently some warnings options which were not
intended for general use were on for a lot of people in eclipse. I
removed all that code from trunk so it won't be an issue in future
revisions. In the meantime you can unclick options like "strict
warnings" which I bet are clicked.