CODEWITHSUNDEEP
javaeclipsecompiler-errors
Evgeniy Dorofeev
Evgeniy Dorofeev

Reputation: 136042

How can Eclipse create a class with unresolved compilation problems?

When I try to compile this class with javac, I get a compilation error and Test.class is not created.

public class Test {
    public static void main(String[] args) {
        int x = 1L;  // <- this cannot compile
    }
}

But when I create this class in Eclipse, I can see that Test.class appears in target/classes. When I try to run this class from command line with java.exe, I get

Exception in thread "main" java.lang.Error: Unresolved compilation problem:
Type mismatch: cannot convert from long to int

Does Eclipse use its own special Java compiler to create a broken .class? How does java.exe know about complilation problems in .class?

Upvotes: 69

Views: 7170

Answers (3)

Rahul
Rahul

Reputation: 45070

If you decompile your class file, you can see the below main() method. That is how the Java compiler knows about the compilation error in the class.

public static void main(String[] paramArrayOfString)
{
    throw new Error("Unresolved compilation problem: \n\tType mismatch: cannot convert from long to int.\n");
}

And all this happens because the compiler (Eclipse Compiler for Java), which Eclipse uses by default/comes bundled with, is not the same as the standard Java compiler!

Upvotes: 66

Erich Schubert
Erich Schubert

Reputation: 8715

Yes, Eclipse uses its own special compiler; known as "ecj". From Stack Overflow question What is the difference between javac and the Eclipse compiler?:

One notable difference is that the Eclipse compiler lets you run code that didn't actually properly compile. If the block of code with the error is never ran, your program will run fine. Otherwise it will throw an exception indicating that you tried to run code that doesn't compile.

Upvotes: 27

Peter Lawrey
Peter Lawrey

Reputation: 533570

Eclipse uses the IBM compiler which has an option of creating classes which do not compile, replacing errors with

throw new Error();

IMHO, this is very bad practice and I have seen some very poor quality projects use this. The project didn't compile completely for weeks at a time.

Unlike fail fast strategies, which try to minimise the cost of bugs, discovering bugs as late as possible also maximises the cost of fixing them.

This strategy only works if you are writing prototype code quickly, i.e. code you know will never get into production. (It is hard to be sure this will be the case)

Upvotes: 42

Related Questions