Merrill,
Properties specified on the command line have always been read-only. The only change that was introduce as part of the 0.85 release, is that a build error is actually thrown when users attempt to overwrite the value of a read-only properties. Previous version of NAnt would just ignore the new value silently, which might introduce unexpected behaviour.
The reason why these properties are read-only is probably to match the behaviour of Ant. I don't think we should change this though ...
Gert
----- Original Message ----- From: "Merrill Cornish" <[EMAIL PROTECTED]>
To: "Gert Driesen" <[EMAIL PROTECTED]>
Cc: "Ian MacLean" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Saturday, August 21, 2004 6:18 PM
Subject: Re: [Nant-users] Params vs properties redux was: Nant .85 not working with Draco.Net
Gert,
All of these immediate problems seem to have arisen not because the readonly attribute was added to properties, but because command line parameters were made readonly. What is the particular advantage of making command line parameters internally readonly?
Merrill
------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
