Re: [jdt-debug-dev] Detecting compilation unit errors? (Bug 1729)

[Darin_Wright@xxxxxxx]

A compiler may produce a class file even when there are compilation errors. If an error is constrained to a method, a compiler can produce byte codes that throw a "compilation error" exception at runtime. 

The way to find errors associated with a class file is to find the corresponding compliation unit, and query its "PROBLEM" markers.

Darin

Marco Qualizza <mqualizza@xxxxxxxxxxxxxxxxxxxx> Sent by: jdt-debug-dev-admin@xxxxxxxxxxx 12/12/2001 07:50 AM Please respond to jdt-debug-dev

To:        Jared Burns <jdt-debug-dev@xxxxxxxxxxx>         cc:                 Subject:        Re: [jdt-debug-dev] Detecting compilation unit errors? (Bug 1729)

Tuesday, December 11, 2001, 7:36:45 PM, you wrote:

> The JavaHotCodeReplaceManager listens to resource changes. When it hears that
> a classfile has changed, it informs running targets and attempts a hot code 
> replace.

> We want to not even attempt the HCR if the compilation unit has compilation 
> errors. Given a class file, is there a simple way to detect if it has errors?

Unless I'm mistaken, but wouldn't a compilation error result in *no*
class file?  Thus, you'd have the old file there and could just do
something as simple as a timestamp check?  Or does the compiler in the
JDT do partial compilations?


-- 
Marco Qualizza

   1. The total sum of human intellect is a Universal Constant.
   2. The Earth's population keeps on increasing.

IE-Engine Canada Inc.
234-2426x226

_______________________________________________
jdt-debug-dev mailing list
jdt-debug-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/jdt-debug-dev