I was about to respond in a similar manner. Filesset is a datatype
basically. So just as you wouldn't name every string variable in C#
String it doesn't make sense to call every fileset <fileset>. I can see
how it makes it easier to remember the tag name when you're editing but
thats the only advantage I could see.
> Well, actually...
> Have you looked at the csc task?
> It has filesets called references, modules, sources... (most of the compile
> related tasks follow this same naming style)
> I would argue that naming things "fileset" is annoying. They should be named
> for their use, not the functionality. :)
> Take <attrib> for example, it has a fileset called "fileset". I would much
> rather this be named "files". The same holds true for <touch>, <move>,
> <copy> and most other file related tasks.
> I'm open to other opinions... :)
> ----- Original Message -----
> From: "Jean Rajotte" <jean@...>
> To: <nant-users@...>
> Sent: Wednesday, April 09, 2003 2:25 PM
> Subject: [Nant-users] a note on the <if> task
>>scott et al,
>>it irks me that the optional fileset isn't called <fileset> but rather
>><comparefiles>. every other task's fileset is called <fileset>. it's
>>not like there's a name conflict within the <if> container.
>>basically, i wish it were called <fileset>.
> This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger
> for complex code. Debugging C/C++ programs can leave you feeling lost and
> disoriented. TotalView can help you find your way. Available on major UNIX
> and Linux platforms. Try it free. http://www.etnus.com
> Nant-users mailing list