Re: Adding another language to the fray

Hmm, just a thought (and please flame me for not
seeing the obvious problems if there are any);

The logical (to me) way to organize languages and
tools and the usage of them, would be to collect all
language specific actions/routes/etc to an .aap file
for the language in question, collect the tools as it is
done today, and when reading a project's recipe;
for each language discovered to be used, import
that language's recipe (which also checks the tools
associated with that language).

I don't really see the reason for importing a
language's actions before they are needed, not
even for C/C++. And with many languages supported, 
this would be the only good way to do it (IMHO).

Lars Ivar Igesund


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