Compiler class refactoring: interface extraction

[ghost]

Wouldn't it be interesting, for future use, to have the Compiler class implement an interface with its essential methods defined in the interface ? That would

1. make future implementations of compilers for other target languages easier, as developers would have a guide
2. enforce a general "same look-and-feel" between future target languages compilers
3. be simple good practice ( "program for interfaces instead of for concrete classes" )

[ghost]

As there is only one public method in Compiler, alternatively we could extract a superclass.

[nobeh]

Hi Jan, I'd suggest having a look at this repo to get started with the tooling: https://github.com/CrispOSS/jabsc-maven-plugin-example

I am not sure if direct jabsc API usage would be of the most convenient way to start coding with it. Thanks.

[ghost]

Thanks for the suggestion, was not or hardly aware of this.

*Fortuna audaces adiuvat - hos solos ? *

On 17 June 2015 at 14:27, Behrooz Nobakht [email protected] wrote:

Hi Jan, I'd suggest having a look at this repo to get started with the
tooling: https://github.com/CrispOSS/jabsc-maven-plugin-example

I am not sure if direct jabsc API usage would be of the most convenient
way to start coding with it. Thanks.

—
Reply to this email directly or view it on GitHub
#16 (comment).