> Would there be any objections to me creating an Interface "Compiler" that
> I can use for programatically calling compilers?
> Currently I have to call all using reflection which is more difficult to
> maintain than simply using an interface. I was thinking of something as
> simple as this:
>
> public interface Compiler {
> int compile(String[] args);
>
> }
>
> And have the default Flex SDK compilers (MXML and COMPC) implement this as
> well as Falcon and the FlexJS compiler. This would make tooling a lot
> easier?
> While at it this interface could contain the definition of the ExitCodes
> to simplify things even more.
>
> What do you think? It shouldn't have any impact on the functionality of
> the Compiler at all, but would make things a lot easier for me and other
> people working on Flex compiler support.
>

You had me at “not have any impact on the functionality" ;-)

+1 if it can be done without needing any chances to current tooling. +0 if
it adds a lot of functionality to (possible) future tools, but would
require some work to adjust current setups. Does this make me sound lazy?
;-)

EdB



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Reply via email to