Gary,

>>> and "best" implies everything else is worse,

I've used a number of large, commercial, and apparently well-documented software 
packages--only to find that what I really needed _was_ a "best practices" document.  
There is a great tendency of documenters to fall into the rut of writing, "...and you 
can do THIS, and you can do THIS, and you can do THIS, and..." for pages on end 
without ever quite stating WHY you would ever WANT to do "this" and what consequences 
to expect.

If the designation of "best" practices bothers  you, we could name it "Pretty Good 
Practices," both as an admission that the field is still evolving and as a nod to the 
PGP people :-) who have done the industry a great service even without offering the 
best in privacy.  But whatever you call it, we _do_ need something at a higher level 
than a list of NAnt tasks.

One small "for example":

I tend to define a NAnt target for each external action a user might want to call the 
NAnt script to do.  Beyond that, I use targets as internal pseudo-subroutines.  As a 
result, my NAnt scripts end up with a relative handful of targets, each of which has a 
_lot_ of procedural code in it.

On the other hand, someone recently posted a zip of a build file that wasn't working 
for him.  His style of doing things was to have many targets, each with mainly trivial 
bodies.

Aside from his style and my style being different, I really would like to know under 
what circumstances one is preferred over the other.  There's probably someone out that 
that knows, but it would be hard for me to find out.  It is quite reasonable to have 
several conpeting "best" practices, each of which applies to different situations.

Merrill


-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM. 
Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php
_______________________________________________
Nant-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-users

Reply via email to