Re: [MinGW-dvlpr] w32api functions...

[Brandon S. <br...@oq...>]

On Sep 8, 2005, at 7:07 AM, Earnie Boyd wrote:

> Drop, probably not; add version filtering, maybe.
>
> *No* we are *not* trying to match the true windows headers, that  
> would break the
> copyright and license agreements.  Your guru friend's changes would  
> not be
> accepted since his changes are based on his reference to the actual  
> MS header. We can only use documentation and a bit of trial and  
> error to commit changes to
> the headers.
>
> Earnie
>

Maybe i was unclear in my email to Chris.   My changes are not based  
on any MS headers, but from the link below.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ 
install/hh/install/cfgmgrfn_3abba546-6876-468e-9dc5-2cb1b286fb9f.xml.asp

Things like AcquireSCMLock don't appear anywhere (that google can  
see) other than WINE/ReactOS, however they're sitting in the mingw  
version of setupapi.def.    I did a search of the platformsdk on  
MSDN, and they don't come up there either.  My question was  
basically, if those routines aren't actually available on the win32  
platform, would it be safe to remove them?   It looks like your  
answer is no, however if i do version them out, any suggestions as to  
the best way to do that?   Does compiling for WINE/ReactOS  
specifically expose any pre-defined stuff i could count on?

Also, to touch on the change rejection.   What you said reads as if  
one has looked at any MS headers in the past, he/she is automatically  
excluded from being able to contribute to the project.   I've been  
doing windows development for well over to a decade, and i'm sure  
i've browsed the MS headers countless times over the years looking  
for values, defines or whatnot to get through a tough spot.   I would  
expect that anyone who started out on a tool other than mingw would  
have done this too.   Does this exclude me from contributing?

I know better than to copy their headers, but this isn't the case.


Brandon