<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 1/31/22 14:44, Eric Pouech wrote:<br>
</div>
<blockquote type="cite"
cite="mid:63b0906d-c2dd-20d6-a25b-1b62191edd21@orange.fr">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div class="moz-cite-prefix">Le 31/01/2022 à 14:24, Nikolay Sivov
a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:2c8cec53-f045-4767-debb-2c412058d8f6@codeweavers.com">Maybe
we could adjust NtGdi prototypes instead. I see a number of
casts like that in existing code already, that would be
unnecessary if DWORD was used for the prototype. <br>
<br>
</blockquote>
<p><font face="Helvetica, Arial, sans-serif">I'm in for avoiding
the casts !<br>
</font></p>
<p><font face="Helvetica, Arial, sans-serif">but, these APIs are
not documented on MS web servers</font></p>
<p><font face="Helvetica, Arial, sans-serif">and I don't have a
ddk handy to check the prototypes</font></p>
<p><font face="Helvetica, Arial, sans-serif">reactos and drmemory
both define ntgdipolypolydraw with a PULONG instead, which
could be a hint, not an absolute confirmation though</font></p>
</blockquote>
<p><br>
</p>
<p><font face="Helvetica, Arial, sans-serif">I think that, since
it's not documented anyway, we may pick the type that works
best, as long as it's binary compatible. Note that some callers
already have casts, because it's sometimes used on INT*,
sometimes on DWORD*, depending on the function. We could avoid
new casts by simply using DWORD or ULONG for </font>NtGdiPolyPolyDraw.</p>
<p><br>
</p>
<p>Thanks,</p>
<p>Jacek<br>
</p>
</body>
</html>