Re: [nant-dev] task question

[Ian MacLean]

Gert Driesen wrote:
----- Original Message ----- 
From: "Ian MacLean" <[EMAIL PROTECTED]>
To: "Ian MacLean" <[EMAIL PROTECTED]>
Cc: "Gert Driesen" <[EMAIL PROTECTED]>; "'Steve Jansen'"
<[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, December 08, 2004 4:20 PM
Subject: Re: [nant-dev] <include> task question

 


Now i just have a question on the naming.
   

That always seems to be our problem ;-)
 

true enough
 

Should we :
A) keep get-buildfile-path() as it is returning the the including file
and add a get-current-file-path() function or
B) change get-buildfile-path() to return the current file and add a
project::get-master-buildfile-path() function to return the including
(ie master ) file .
( as demonstrated above )
   

We could also add a bool argument to project::get-buildfile-path().
BTW: Would this return the parent build file, or the top build file ? What
if we have nested includes ?
What about the other project functions :
project::get-base-directory
project::get-buildfile-uri
project::get-default-target
project::get-name
 

probably won't need get-name as the included file gets merged into the 
including file and loses its name at that point.

I think we're gonna need an all or nothing solution for this problem. It
doesn't make sense to provide a solution for just one the project functions.
 

of course - It might actually make sense to put functions dealing with 
the current file outside the project namespace - not sure what to call 
it though.

Ian

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers