Thanks for your opinion Gert, comments inline:
> - its easier to distinguish properties (as Ian originally said)
definitely, but in C#/JScript you don't have variable prefixes either, yet
the programs are easily understandable
> - it won't break compatibility for properties with numeric names (eg
${123})
Can you have properties with such names? What's the use for them? Maybe they
should be disallowed or deprecated?
> - corresponds with the MSbuild implementation. (not that this is
importantà
MSbuild is much simpler and looks like it only supports string types so they
have fewer problems with string quoting, etc.
> - XSLT also uses a ($) prefix for variables
This could be easily implemented in expression evaluator, but I'm not
convinced that this should be done.
We have 3 options:
1. if=${length(${propertyname})=length(${someotherpropertyname})}"
2. if=${length($propertyname)=length($someotherpropertyname)}"
3. if=${length(propertyname)=length(someotherpropertyname)}"
1 is ugly IMHO (too many embedded curly braces which are unreadable with
proportional font), 2 is acceptable because you can easily tell properties
from functions and 3 is beautiful.
What do you think?
> I also don't think we should use lt, gt, ... instead of ==, > for
operators,
> both XSLT and MSBuild use similar operators ... so I don't see why we
should
> be different ...
OK. Let's keep them as < >...
Jarek
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
