Re: (resend) shlwapi: implement StrChrNW

[Jacek Caban]

Hi Aric,

Aric Stewart wrote:
> ---
>  dlls/shlwapi/shlwapi.spec |    1 +
>  dlls/shlwapi/string.c     |   23 +++++++++++++++++++++++
>  2 files changed, 24 insertions(+), 0 deletions(-)

I didn't test it myself, but StrChrNW name suggests, that the search 
shouldn't be case insensitive.


Jacek

(resend) shlwapi: implement StrChrNW

[Aric Stewart]

MSDN states that "The comparison is not case-sensitive"

-aric

Jacek Caban wrote:
> Hi Aric,
>
> Aric Stewart wrote:
> > ---
> >  dlls/shlwapi/shlwapi.spec |    1 +
> >  dlls/shlwapi/string.c     |   23 +++++++++++++++++++++++
> >  2 files changed, 24 insertions(+), 0 deletions(-)
>
> I didn't test it myself, but StrChrNW name suggests, that the search 
> shouldn't be case insensitive.
>
> Jacek

(resend) shlwapi: implement StrChrNW

[Paul Vriens]

On 09/24/2009 04:04 AM, Aric Stewart wrote:
> MSDN states that "The comparison is not case-sensitive"
>
> -aric
>
> Jacek Caban wrote:
> > Hi Aric,
> >
> > Aric Stewart wrote:
> > > ---
> > > dlls/shlwapi/shlwapi.spec | 1 +
> > > dlls/shlwapi/string.c | 23 +++++++++++++++++++++++
> > > 2 files changed, 24 insertions(+), 0 deletions(-)
> >
> > I didn't test it myself, but StrChrNW name suggests, that the search
> > shouldn't be case insensitive.
> >
> > Jacek

Isn't this the perfect opportunity for a conformance test ;)

-- 
Cheers,

Paul.

(resend) shlwapi: implement StrChrNW

[Alexandre Julliard]

Aric Stewart <aric(a)codeweavers.com> writes:
> MSDN states that "The comparison is not case-sensitive"

Considering that there is also a StrChrNIW, it's a pretty safe bet that
MSDN is once again on crack.

-- 
Alexandre Julliard
julliard(a)winehq.org

(resend) shlwapi: implement StrChrNW

[Aric Stewart]

I will write up a conformance test to check. It should not be too hard.

thanks,
-aric

Alexandre Julliard wrote:
> Aric Stewart <aric(a)codeweavers.com> writes:
> > MSDN states that "The comparison is not case-sensitive"
>
> Considering that there is also a StrChrNIW, it's a pretty safe bet that
> MSDN is once again on crack.