I agree with you there but the way If is implemented it considers all parameters for the condition. You could limit the task to accept only one logic parameter but then you are limiting its power.
-----Original Message----- From: Scott Hernandez [mailto:[EMAIL PROTECTED]] Sent: Monday, July 22, 2002 4:20 PM To: 'Nant-Developers (E-mail)' Subject: RE: [nant-dev] IFTask PropertyMissing parameter? I was kinda leaning towards an <if> with a not. It is a little more generic, and doesn't require us to add the negative condition to all the tests. > -----Original Message----- > From: Kevin Miller > Sent: Monday, July 22, 2002 2:16 PM > To: Nant-Developers (E-mail) > Subject: [nant-dev] IFTask PropertyMissing parameter? > > Does anyone have a problem with adding a property to the If task allowing > you to check to see if a property is missing? The reason I see the need > for > this is to test for negations. For instance if I use Nant to invoke a > child > build with inherit all. The childscript may not wish to override > properties > passed in by the parent. It can then test if the property is missing > > <if propertymissing="debug"> > <property name="debug" value="true" /> > </if> > > I understand you may not want NAnt to become a scripting language so if > you > have another suggestion to accomplish this please let me know. > > Kevin Miller ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
