Hi, * Troy Laurin wrote on 13.07.2004 (15:57): > Defining namespace in the class defining the task is an interesting idea > and a possible solution... it's worth comparing this with the other > viable solutions to see what's the best solution, both in terms of > functionality as well as correctness and convenience.
On my way to work, I thought on my proposal. I wouldn't use a seperate attribute but changing the task attribute instead. The pro is, that we can rely that there *is* a namespace associated with each task. The con is, that it would require a rework on all tasks. A second con came into my mind, but it left as fast as it came: Giving all nant tasks a namespace would require a <nant:csc>...</nant:csc> instead of <csc>...</csc>. To avoid this, give the project a property defaultnamespace which is set to nant per default, but may be overriden by the user. > Rather than continuing this discussion (in particular, compare & > contrast) on this list, is it worth creating a page for the > requirements/semantics of namespace support to the nant wiki pages? I don't have a problem discussing it here or on the wiki. Just tell me where discussion is running ;) -sa -- sa at programmers-world dot com http://www.livingit.de Internet sites: http://www.not2long.net - Make long links short Boomarks online: http://www.mobile-bookmarks.info ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
