Re: Adding default tool

----- Original Message ----- 
From: "Bram Moolenaar" <[email protected]>
> 
> You copied the action for the "c" filetype, right?  Then you need to
> remove the check for "COMPILE_ACTION".  Or rename it to
> "D_COMPILE_ACTION".

Using D_COMPILE_ACTION made it work as I wished.

> 
> The idea is that the default action works on most platforms.  Like the
> "cc" programs can mostly be used to compile a C program.  The tools are
> for setting up the compiler on a specific platform.
> 
> 
> I have wondered if this variable would have to be called
> "C_COMPILE_ACTION".  But the same variable is used for C++, since it is
> usuallly the same compiler.  Hmm, perhaps we should use
> CXX_COMPILE_ACTION for that, since the tool can set both variables.
> 
> Changing this would be incompatible with Aap version 1.0, and I promised
> not to make incompatible changes.  Opinions?

I don't object to COMPILE_ACTION defaulting to C/C++. Would it break
compability if all tools set COMPILE_ACTION plus 
{language}_COMPILE_ACTION? Thus the D compiler could become
the default tool if no compilers for other languages are present. Or maybe
there is no point as long as I need to use D_COMPILE_ACTION in the
relevant action bodies?

Other languages that it would be natural to have COMPILE_ACTION variables
for would at least include FORTRAN. Maybe Java?

Lars Ivar Igesund 


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf