Affects Version/s: X10 1.7.3
Fix Version/s: X10 2.0.4
Environment:Eclipse 3.3.2, x10.common.17_126.96.36.199.jar, x10.compiler.p3_188.8.131.52.jar, x10.constraints_184.108.40.206.jar, x10.runtime.17_220.127.116.11.jar
-commandlineonly option set in X10 preferences.
Number of attachments :
There continues to be issues with compilation stopping in the middle when there are errors in one file.
We used to have this in X10 v1.5 and then Bob had done something to fix this.
The symptom is that you get lots of errors in the Problems window.
But then you clean, and now you get a different set of errors.
Try this on a project which has multiple X10 source files.
I was working on the xcc.lang files when I noticed this.
What is the semantics of -commandlineonly when used from within X10DT? i.e. what happens when I edit some text in a file? With what files is the X10 compiler invoked? What happens when I save a file? Does it invoke x10c only with that file? That could be a problem. Perhaps it should invoke with all files in the user project...?