Hi Gerry,
> > I'm wary of using whitespace as a delimiter.
>
> Right now target names are delimited by white space.
OK, I should've seen that one coming :)
I should've been more specific: I don't like line separators (whatever you
defined them as) as delimiters for this kind of thing.
> If you need to have a string with spaces you need to use a different
method
> (ie, the <includes name=""/> style).
See, that's one of the things I don't like, precisly. If the whole intention
is to make it easier for people to read and write buildfiles, having to do
things in two different ways depending on such a simple thing doesn't make
it easier at all... only more confusing, in my mind.
But it does bring two questions I haven't seen addressed in your posts:
- Would you consider keeping supporting the <includes ...> ? As long as
that's there, I'd be happy, as I probably wouldn't use the other one :)
- If people had the "strings with spaces" issue, what would be the supported
way to address it? There are a few options I see:
- Make every entry in the fileset use the <includes > syntax
- Allow mixed content in the fileset element (yuck!)
- Allow you to split the fileset in two elements (yuck, too)
--
Tomas Restrepo
[EMAIL PROTECTED]
-------------------------------------------------------
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
