Martin, just read through your previous thread.
I think that XML-based communication between tasks and the trycatch task have different purposes. Specifically, trycatch is a flow control device. Flow control can certainly be reproduced with increased task verbosity, but using a flow control device to describe flow conveys much more intent, which makes build files (IMHO) easier to read... or rather, easier to interpret correctly. I'm not sure how much I agree with xml output for tasks. I can see how it would be useful in theory for chaining together tasks with strong dependencies... but in practice, if a particular task is so dependent on the output of another task, then why doesn't it extend (or compose) the other task. This allows the task to communicate with its predecessor in the trivial way, through object properties and method calls, without having to modify how NAnt works. The best example I have of this concept is the solution task. All of the tools and tasks (more or less) required to simulate the solution task are available... they could be extended with verbose outputs to allow chaining them together, but it is much more useful as a single task, which composes its required tasks and facilitates communication between the tasks. Perhaps the problem is just that I can't think of an example for which verbose inter-task communication would be a good fit. Do you have an example that is more extensive than the exec example that you can share? Regards, -- Troy > -----Original Message----- > From: Martin Aliger [mailto:[EMAIL PROTECTED] > Sent: Friday, 9 July 2004 2:40 PM > To: Gert Driesen; Troy Laurin; Nant-Developers (E-Mail) > Subject: Re: [nant-dev] trycatch task ? > > I think both are cases of inter-task communication. IMO > current nant is totally missing such communication. > errorproperty proposal is very limited implementation of such > communication. I'd rather prefer making something more robust > enabling more advanced scenarios like examining what failed > or what was skipped (mainly in complex tasks like <solution>) etc. > > Some time ago I propose XML-like based communication - maybe > its time comes? > How do you see it now when there was enough time to consider it? > > <trycatch> task is also good addition in mine eyes. I > personally dont see anything bad in implementing both - > trycatch and some kinf of communication in the same time. > Different scenarios should use different approaches > > Regards, > Martin Disclaimer Message: This message contains confidential information and is intended only for the individual(s) named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. To the maximum extent permitted by law, Immersive Technologies Pty. Ltd. does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
