Re: cabinet: Include wine/port.h for strcasecmp().

2008-02-01 Thread Bang Jun-young
On 2/1/08, Francois Gouget <[EMAIL PROTECTED]> wrote: > The rules are as follows: > > * For case insensitive comparisons of 'windows strings', a Windows >function must be used (stricmp() or similar). In this case, KERNEL32 lstrcmpiA() would be more appropriate. In general, using stricmp() in

Re: What's needed to make gdb work again?

2008-02-01 Thread Eric Pouech
Maarten Lankhorst a écrit : > Hi folks, > > I've been trying some debugging with kdbg (Graphical kde debugger), but > it fails on wine because it can't attach to a process. > > While it is of course possible to use WINEDEBUG flags, I want to be able > to use a full debugger, and not just deduce fro

Re: test.winehq.org

2008-02-01 Thread Francois Gouget
On Thu, 31 Jan 2008, Reece Dunn wrote: [...] > Also, the security tests (the previous one) have two output lines, e.g.: > > security: 18 tests executed (0 marked as todo, 0 failures), 0 skipped. > security: 944 tests executed (0 marked as todo, 0 failures), 1 skipped. Yes, this typically happ

Re: cabinet: Include wine/port.h for strcasecmp().

2008-02-01 Thread Francois Gouget
"Bang Jun-young" <[EMAIL PROTECTED]> wrote: >> > cabinet: Include wine/port.h for strcasecmp(). >> >> If a Wine DLL uses strcasecmp() then it's a bug. It should >> use an appropriate kernel32 API instead. > > I know, but it's too late. The tree is already contaminated with such > functions and

Re: Review comparing Wine and Vista for running games

2008-02-01 Thread Jeff Latimer
Bang Jun-young wrote: > I think this kind of a silly game doesn't help Wine as much... > It may not be a help but like they say "there's not such thing as bad publicity". A lot more people hear of Wine is better than not hearing about it.

Re: cabinet: Include wine/port.h for strcasecmp().

2008-02-01 Thread Dmitry Timoshkov
"Bang Jun-young" <[EMAIL PROTECTED]> wrote: >> > cabinet: Include wine/port.h for strcasecmp(). >> >> If a Wine DLL uses strcasecmp() then it's a bug. It should >> use an appropriate kernel32 API instead. > > I know, but it's too late. The tree is already contaminated with such > functions and qu