<div dir="ltr"><div><div><div>Yes, maybe it would have worked, I don't know.<br></div></div>Analyzing if this warning is a true or false positive is costly and it's hard to store the result of the query.<br></div>The best thing to do is to just eliminate the warning by providing compatible types.<br></div><div class="gmail_extra"><br><div class="gmail_quote">2016-07-08 14:46 GMT+02:00 Henrik Sperre Johansen <span dir="ltr"><<a href="mailto:henrik.s.johansen@veloxit.no" target="_blank">henrik.s.johansen@veloxit.no</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Reading<br>
<a href="https://msdn.microsoft.com/en-us/library/windows/desktop/bb773352(v=vs.85).aspx" rel="noreferrer" target="_blank">https://msdn.microsoft.com/en-us/library/windows/desktop/bb773352(v=vs.85).aspx</a><br>
Wouldn't either way work?<br>
The struct field is a UINT ID number, not a pointer, so truncating the<br>
pointer to use as id would be as good as putting a 64bit pointer in the<br>
struct, and then overwriting the last bits by subsequently setting uFlags,<br>
as long as they both consistently yield the same value in uID field based on<br>
hInstance.<br>
<br>
<br>
<br>
<br>
--<br>
View this message in context: <a href="http://forum.world.st/OpenSmalltalk-opensmalltalk-vm-931559-Replace-another-UINT-cast-by-usqIntptr-t-for-L-tp4905547p4905579.html" rel="noreferrer" target="_blank">http://forum.world.st/OpenSmalltalk-opensmalltalk-vm-931559-Replace-another-UINT-cast-by-usqIntptr-t-for-L-tp4905547p4905579.html</a><br>
Sent from the Squeak VM mailing list archive at Nabble.com.<br>
</blockquote></div><br></div>