Shaw, Gerry wrote:

>>I think its a good idea. Howver the outer tag should probably be 
>>    
>>
><propertygroup> or somthing like that. I think the . seperator is fine. 
>
>Do others feel strongly about this?  I have it working with <property
>prefix="....">.  I like it being all in one task so that when the user reads
>the docs for <property> they understand everything about it.
>
>Note that they can be nested as well.  Ie,
>
><property prefix="win">
>    <property prefix="vc7">
>        <property name="cc" value="cl.exe"/>
>    </property>
></property>
>
>Would give: win.vc7.cc = "cl.exe"
>
>  
>
what happens if you put a value on the top level property ? I don't know 
it seems to add confusion to my mind. Ant allows the <property> tag to 
reference a file containg a list of properties. I thought this was also 
a mistake. Overloading property to mean single property in some cases 
and set of properties in another is confusing to me. Documenting them in 
the one place is a seperat issue. I'm sure we can do that without having 
to overload <property> to mean different things.

>>I don't see a need for allowing custom seperators - it just seems to me 
>>    
>>
>that it would add unnecessary confusion. '.' is already a pseudo 
>standard by its use for 'nant'. properties.
>
>I agree for most cases but it doesn't really hurt to add it and it adds the
>ability to use it in ways we haven't thought of.
>
Again I disagree. In too many open source projects there are too may 
things added as options because people can't agree on sensible defaults. 
To use it or abuse it ? If I come across a build file that uses # then $ 
then ^ as seperators I'd start screaming. Its like allowing you to use # 
or % as namespace seperators in C#. In fact its solving the same 
problem. We don't need to be creating another Perl :)

>  
>
Ian

-- 
"The use of COBOL cripples the mind; its teaching should, therefore, be regarded as a 
criminal offence." (Edsger Wybe Dijkstra)




-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
Nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

Reply via email to