Dmitry Timoshkov wrote:
Paul Bryan Roberts pbronline-w...@yahoo.co.uk wrote:
It appears that GetNamedSecurityInfoExA signature doesn't match
the MSDN/PSDK one. Also it's a common practice to simultaneously
add both A and W versions, and add prototypes to an appropriate
.h file.
Ah, right
Paul Bryan Roberts pbronline-w...@yahoo.co.uk wrote:
I did reference the piclist web-page in the analysis I attached to bug
14334 but accept that no one is ever likely to read it.
The description of API parameters in your patch looks like directly copied
from that page, so you should either
Dmitry Timoshkov wrote:
Paul Bryan Roberts pbronline-w...@yahoo.co.uk wrote:
I guess this stub falls in to the 'not obviously correct' category.
I could do with some feedback on what might be an acceptable patch.
It appears that GetNamedSecurityInfoExA signature doesn't match
the
Ah, right you are, thanks.
I guess that should have read 'most obviously incorrect'.
I cannot find any reference to GetNamedSecurityInfoEx with or without
the A or W on http://www.msdn.microsoft.com. I have looked several
times over the last six months or so. Is there another MSDN
Paul Bryan Roberts pbronline-w...@yahoo.co.uk wrote:
It appears that GetNamedSecurityInfoExA signature doesn't match
the MSDN/PSDK one. Also it's a common practice to simultaneously
add both A and W versions, and add prototypes to an appropriate
.h file.
Ah, right you are, thanks.
I
Paul Bryan Roberts pbronline-w...@yahoo.co.uk wrote:
I guess this stub falls in to the 'not obviously correct' category.
I could do with some feedback on what might be an acceptable patch.
It appears that GetNamedSecurityInfoExA signature doesn't match
the MSDN/PSDK one. Also it's a common
