Please explain reason for the wording of this error message

[Ronald Otto]

I erroneously wrote the following crap in my

catch

-block:

try {
   ...
}
catch(Exception e) {
            System.out.println("EXCEPTION "+e.class);
            System.out.println(e.getMessage());
            System.exit(1);
}

The correct way to write it is

System.out.println("EXCEPTION "+e.getClass());

Of course, the compiler complained about my code, but I found it interesting, how it complained:

wpsel.java:34: cannot find symbol
symbol  : class e
location: class wpsel
            System.out.println("EXCEPTION "+e.class);
                                            ^
1 error

The error message says, that the symbol e was not found. How come? Of course, e is a known symbol here (and if I replace the incorrect class by the correct getClass(), I don't get a compiler error anymore.

[K. Tsang]

Welcome to the Ranch.

My explanation may not be the best so I give it a try.

When you use ".class" (with the dot) the compiler/JVM is really looking for that class file/bytecode.

So in your case, the compiler is looking for the class called "e" in your project or Java API, which there isn't one. "e" is a variable, the compiler doesn't know you are referring to the "Exception.class" if you do "e.class".

Therefore using "e.getClass()" will resolve that to the Exception.class

[Dave Tolls]

Can I just suggest that, instead of printing the class and message, you do:

e.printStackTrace();

You will miss a lot of info if you don't do that, including the exact line that is causing your exception, and any exception chains.

[Winston Gutkowski]

K. Tsang wrote:When you use ".class" (with the dot) the compiler/JVM is really looking for that class file/bytecode.

A couple of things:
1. It can't be the JVM, because it's a compiler error.
2. It can't be looking for a class file because it may not be compiled yet.

But you're absolutely correct that it's looking for something - a Class name.

@Ronald: I agree with you; the message is badly worded - although that may have something to do with the way that it checks these things.

But not being a compiler writer, it's all I can offer.

Winston

PS: Welcome to JavaRanch, Ronald.