ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Conor MacNeill <>
Subject Re: ant 1.5.4 : Import
Date Thu, 24 Jul 2003 23:15:20 GMT
On Fri, 25 Jul 2003 01:44 am, Kenneth Wood wrote:
> Well, that's convenient, but not necessarily what I would have expected.
> A C or C++ program doesn't include another  program just
> to get definitions. Instead, the definitions are put into
> a ".h" file, and both programs import that ".h" file of definitions.
> So, the definitions of locations could be in
> a "locations.xml" file, then imported by Ant's build.xml and your check.xml
> allowing both build files to share the definitions, but not pull in any
> unwanted
> things.

Sure. Let me push the C/C++ analogy a little further. The use of .h files is 
actually just a convention built upon the #include machanism. The underlying 
mechanism does not prevent you from #including other file types, including 
code. In fact many C++ programs include .c files containing inline code. 

The analogy with Ant breaks when we talk about target overriding which will be 
a useful usecase. You can't override code in C++.

So, the use of a locations.xml file to share property defs would be fine. In 
fact it may emerge as a standard convention built on the import mechanism. It 
does not mean, however, that import should be restricted from importing other 
complete build files.

BTW Ken, check out the <parallel> changes - finally made it.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message