First of all: I sent a new DPA testsuite to wine-patches some hours ago
(http://tinyurl.com/ddlp4) which tests DPA_InsertPtr() with both (nItems
< idx < 0x7fff) and (0x7fff < idx).
Our behaviour does not match Windows in both cases (besides several
other differences). The tests are marked as t
Hi,
> > In lines 1944 and 1977 of dlls/comctl32/comctl32undoc.c the value
> > "0x7FFF" is used to check for the boundary of a 32 bit integer. However,
> > there should be used MAX_INT instead.
> I somehow doubt that this function will ever encounter an INT greater
> than MAX_INT... :)
you're of
Sascha Cunz wrote:
In lines 1944 and 1977 of dlls/comctl32/comctl32undoc.c the value "0x7FFF" is
used to check for the boundary of a 32 bit integer. However, there should be
used MAX_INT instead.
I somehow doubt that this function will ever encounter an INT greater
than MAX_INT... :)
Anyway
Hi,
playing around a bit with wine, i found a thing that is obviously a bug.
In lines 1944 and 1977 of dlls/comctl32/comctl32undoc.c the value "0x7FFF" is
used to check for the boundary of a 32 bit integer. However, there should be
used MAX_INT instead.
By the way: Looking at current MSDN, DPA
