On Thu, 21 Mar 2002 22:24, stephan beal wrote: > On Thursday 21 March 2002 13:04 pm, Adam Murdoch wrote: > > > --- Adam Murdoch <[EMAIL PROTECTED]> wrote: > > > > You're not the only one. In myrmidon, we changed if and unless to > > > > test the property value against true/false/yes/no (with unset still > > > > evaluating to false). > > > > > > And I assume set (to anything) will evaluate to true? > > > > Here's how the test gets evaluated: > > > > property not set => false > > property set to 'false' => false > > property set to anything other than 'false' => true > > That's how it SHOULD get evaluated, IMO, but that's not how it actually > works > > (at least, in Ant 1.4.1). It goes like this:
Adam was referring to the "Myrmidon" ant2 proposal, not to a current release of Ant. Hopefully, in the not too far distant future, you'll be able to download it and try it out yourself. > Then again, maybe it only responds to the word 'false', and not 'off' or > 'no', as most other flags do? I'll look at adding support for "off" and "no" when I convert the Myrmidon <if> task to use a new IfCondition. ciao Daz -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
