Hi Bertrand > I learned programming back when waiting for a compilation meant going > out for a coffee (or lunch if you still had floppy disks ;-), and > still appreciate some effort before compiling, to try and be a bit > careful...YMMV of course.
I come from this ancient long past time as well :-)) And yes, I certainly agree, it's worth to have a deep look at the code before compiling - even if compiling is much more faster today. > If I find an easy way to have hyperlinks from compilation errors, I > will probably activate it, but right now I prefer not having to worry > too much about my IDE. You could say that I use Eclipse as an editor / > code browser / pre-compilation analyzer / coding assistance tool / > debugger, that's a lot already, it just not include the build cycle. I tried your setup and it doesn't feel (as it seems on a first view) that unproductive. You haven't to turn off the Java Builder needfully. Let it turned on, you get all the compiling warnings and errors as usual. best regards mike
