On Tuesday 20 January 2004 11:02, Francois Gouget wrote:
> Arg. Spoke a bit too quick in my previous email. This patch introduces a
> new problem. When verifying the generated.c files I see a lot of diffs
Well, it merely uncovers two more cases of reference variable
misuse. Revised patch attached
On Tue, 20 Jan 2004, Hans Leidekker wrote:
[...]
> That code is mixing up the use of a variable holding a string
> and a variable holding a reference. Put otherwise it forget's
> to dereference a scalar ref (similar to a C pointer variable)
> before using it. Patch below fixes it.
Arg. Spoke a bit
On Tue, 20 Jan 2004, Hans Leidekker wrote:
> On Tuesday 20 January 2004 14:09, Francois Gouget wrote:
>
> > include/winuser.h: DWORD[CCHILDREN_TITLEBAR+1]: can't parse type
> > ('DWORD') ('CCHILDREN_TITLEBAR+1')
> > Can't use string ("4") as a SCALAR ref while "strict refs" in use at
> > tools/win
On Tuesday 20 January 2004 14:09, Francois Gouget wrote:
> include/winuser.h: DWORD[CCHILDREN_TITLEBAR+1]: can't parse type
> ('DWORD') ('CCHILDREN_TITLEBAR+1')
> Can't use string ("4") as a SCALAR ref while "strict refs" in use at
> tools/winapi/c_type.pm line 283.
That code is mixing up the use
When I run ./tools/winapi/winapi_test it chokes on the TITLEBARINFO
declaration in winuser.h:
typedef struct tagTITLEBARINFO {
DWORD cbSize;
RECT rcTitleBar;
DWORD rgstate[CCHILDREN_TITLEBAR+1];
} TITLEBARINFO, *PTITLEBARINFO, *LPTITLEBARINFO;
include/winuser.h: DWORD[CCHILDREN_TIT
