Examples of com.redhat.ceylon.compiler.java.launcher.Main$ExitState

com.redhat.ceylon.compiler.java.launcher.Main

Rich information about the failure (or success) of a compilation. The factory methods on this class serve as a mapping between javacs error handling, and that required for ceylon.

Gory details

Ceylon Syntax and Type Errors

A `JavacAssertionVisitor` logs an `error()` with key "compiler.err.ceylon" on the javac `Log` (which happens to be a `CeylonLog`)

Exceptions throw during codegen

A `JavacAssertionVisitor` logs an `error()` with key "compiler.err.ceylon.codegen.exception" on the javac `Log` (which happens to be a `CeylonLog`)

`makeErroneous()`

Logs an `error()` with key "ceylon.codegen.erroneous" on the javac `Log` (which happens to be a `CeylonLog`) and returns an `Erroneous`

`Tree.JCErroneous`

`Attr` produces an error for these.

`Diagnostic` keys

`Diagnostic`s in the javac `Log` which don't have a message code beginning with "compiler.err.ceylon" must therefore be due to codegen generating an AST which isn't accepted by javacs typechecker. I.e these represent a bug in codegen.

IDE Error reporting

The IDE uses a javac `DiagnosticListener` to find out about errors

    }
    
    @Override
    public void initialize() throws IOException {
        setSystemProperties();
        compiler = new Main("ceylon compile");
        Options options = Options.instance(new Context());
        
        if (modulesOrFiles.isEmpty() &&
                !javac.contains("-help") &&
                !javac.contains("-X") &&

        if (diagnosticListener != null && context.get(DiagnosticListener.class) == null)
            context.put(DiagnosticListener.class, diagnosticListener);


        context.put(JavaFileManager.class, fileManager);
        JavacTool.processOptions(context, fileManager, options);
        Main compiler = new Main("ceyloncTask", context.get(Log.outKey));
        return new CeyloncTaskImpl(compiler, options, context, classes, compilationUnits);
    }