Omkar Shetkar wrote:Here, I am curious to know why Java compiler spits out same error in different places. Isn't it enough to give compilation error at line 4 and end compilation.
Once it knows that abstract class is not implemented correctly, there is no point in going further compiling.
Roel De Nijs wrote:
And it's a good thing you get as many compiler errors as possible at once, because now you can fix them all at once instead of having to go through the cycle "compile & fix compiler error" many times.
Omkar Shetkar wrote:IMHO, I would regard this as "kind of inconsistency" from Java compiler.
Is it the case that compiler follows some kind of rules which prioritizes compilation errors?
Am I missing something here ?
Omkar Shetkar wrote:If I rename Puma to int keyword, then I get following errors