Home >Java >javaTutorial >Eclipse Compiler (ECJ) vs. javac: Is it Just a Wrapper or a Distinct Compiler?
Eclipse Compiler vs. javac: Unveiling the Differences
While Eclipse is renowned for its comprehensive IDE suite, a common question arises: Is the Eclipse Java compiler merely a wrapper around the javac compiler bundled with the Java SDK? To elucidate this matter, we embark on an exploration of the differences between these two compilers.
Distinct Implementations
Contrary to the notion of a shared core, Eclipse has developed its own compiler, known as the Eclipse Compiler for Java (ECJ). This compiler deviates from javac in several crucial aspects.
Incremental Compilation
One striking distinction lies in ECJ's support for incremental builds within the Eclipse IDE. As you type, code is parsed and compiled on the fly, facilitating a continuous development cycle without the need for manual compilation steps.
Tolerance for Errors
A peculiar feature of ECJ is its ability to permit the execution of code that may not have compiled without errors. If the problematic code is not encountered during runtime, the program proceeds as expected. Otherwise, an exception is thrown, alerting the developer to the unresolved issue.
Additional Differences
Conclusion
Eclipse's Java compiler, ECJ, emerges as a distinct implementation with unique capabilities compared to javac. Its support for incremental compilation, tolerance for errors, and seamless integration within the Eclipse IDE enhance the development workflow for Java developers. While javac remains the standard compiler for command-line compilation, ECJ has earned its place as a preferred choice for certain scenarios and within the Eclipse development environment.
The above is the detailed content of Eclipse Compiler (ECJ) vs. javac: Is it Just a Wrapper or a Distinct Compiler?. For more information, please follow other related articles on the PHP Chinese website!