Vincent Béron wrote:
Besides the fact that HIDWORD and LODWORD (typo in LODDWORD) do not
exist,
Yes, I was extrapolating on existing macros for readability.
it looks fine as long as you don't actually compile it.
Writing those two and compiling yields the error "initializer element is
not constant"
Le dim 17/10/2004 à 01:24, Shachar Shemesh a écrit :
> Vincent Béron wrote:
>
> >Le sam 16/10/2004 à 23:54, Dmitry Timoshkov a écrit :
> >
> >
> >>"Vincent Béron" <[EMAIL PROTECTED]> wrote:
> >>
> >>
> >>
> >>>We try to put a pointer in a DWORD in a static initialization of
> >>>CRITICAL_SEC
Vincent Béron wrote:
Le sam 16/10/2004 à 23:54, Dmitry Timoshkov a écrit :
"Vincent Béron" <[EMAIL PROTECTED]> wrote:
We try to put a pointer in a DWORD in a static initialization of
CRITICAL_SECTION_DEBUGs. Of course it doesn't work on Win64. We'll have
to find a better solution though.
Le sam 16/10/2004 à 23:54, Dmitry Timoshkov a écrit :
> "Vincent Béron" <[EMAIL PROTECTED]> wrote:
>
> > We try to put a pointer in a DWORD in a static initialization of
> > CRITICAL_SECTION_DEBUGs. Of course it doesn't work on Win64. We'll have
> > to find a better solution though.
>
> Another w
"Vincent Béron" <[EMAIL PROTECTED]> wrote:
> We try to put a pointer in a DWORD in a static initialization of
> CRITICAL_SECTION_DEBUGs. Of course it doesn't work on Win64. We'll have
> to find a better solution though.
Another way to fix it is to use full 'DWORD Spare[2]' to store a pointer
on W
