ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran" <stev...@iseran.com>
Subject Re: [PATCH] some diffs to ExecTask
Date Sun, 25 Nov 2001 19:08:15 GMT

----- Original Message -----
From: "Peter Donald" <peter@apache.org>
To: "Ant Developers List" <ant-dev@jakarta.apache.org>
Sent: Sunday, November 25, 2001 2:30 AM
Subject: Re: [PATCH] some diffs to ExecTask


> On Sun, 25 Nov 2001 17:22, Steve Loughran wrote:
> > I'm dont want to commit these until people have had a look at the
changes
> > and are happy with them.
> >
> > Apart from some tabs to spaces conversion , the two big changes here are
> >
> > 1. you can specify a resultproperty that saves the result value into an
> > (undefined) property. Obviously only of relevance if failonerror=false
>
> Whats the use case of this? Is it just a work around for limitations of
ants
> error handling behaviour?

two use cases.

Case 1, have some win32 wrapper around a com object whose return code is an
HRESULT; any retval <0 is a failure, any result >= success. So to call it to
register stuff needs some better post processing.

Case 2. Another native win32 app, this one using cryptoapi to talk to the
hardware random number generator in the i815, i820 and intel xeon server
chipsets. Not quite as impressive as using a neutrino detector to generated
randomness, but it doesnt need the handy salt mine and isnt so vulnerable to
people on the other side of the planet pointing neutrino beams at it and so
being less random than you want. The app just returns the number as the
return code; this makes it easy to use from java apps without doing any JNI
stuff. Saving the output of an exec to a property would let me use it in a
build, even though I dont actually have a need for that right now.

-steve




--
To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>


Mime
View raw message