Re: Path-related asserts

"Kelly Anderson" <[email protected]>
Newsgroups gmane.comp.windows.dotnet.nunit.devel
Message-ID <[email protected]>
You clearly wouldn't want to do this all the time since case is
significant on many directory systems. I could be missing your point.

-Kelly

On Fri, Feb 15, 2008 at 1:33 PM, Daniel M. Pomerantz
<[email protected]> wrote:
> I was thinking about this a little bit, and I came up with a suggestion:
>
>  Any assert that is based on tests, allow a parameter to them "bool
>  ignoreCase" which is passed into the String.Compare().  Users of these
>  asserts can do what they feel is best.  For instance, you could do your
>  test of Path.DirectorySeperator, and I could always tell it to ignore case.
>
>  You can also include overloads of those asserts which omit that
>  parameter, just like String.Compare does.  If the parameter is omitted
>  either always ignore case, or never omit case.  Do not base it on the
>  OS, since as discussed it is not OS dependant.  I am in favour of always
>  ignoring case, but I could see either way.  Whichever, this will provide
>  some consistancy.  Whatdya say?
>
>  dmp
>

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.