RE: [Mingw-users] Missing WTS defines

[Wells, R. K. <ROG...@sa...>]

Anyone can certainly get to that list of definitions without ever having
installed the SDK however.

Roger Wells, P.E.
SAIC
221 Third St
Newport, RI 02840
401-847-4210 (voice)
401-849-1585 (fax)
rog...@sa...
-----Original Message-----
From: min...@li...
[mailto:min...@li...] On Behalf Of Keith MARSHALL
Sent: Friday, March 17, 2006 5:13 AM
To: min...@li...
Subject: Re: [Mingw-users] Missing WTS defines

Pierre Ossman wrote, quoting me:
>> Pierre Ossman wrote:
>>> The following WTS related defines are missing from winuser.h:
>>>
>>> [block of defines snipped]
>> 
>> How have you determined the values you've posted?  If you've
>> simply copied them from a Microsoft SDK header, then we can't
>> use them.
>
> That I did. But a series for codings for publically available names
> can hardly claim the benefit of copyright protection.

But by simply copying them, you violate the EULA to which you
subscribed when you installed the SDK, (whether you actually read it
or not is immaterial).

> Where would the line be drawn in that case? Would a binary doing:
>
>                printf("DEFINE: %d", DEFINE);
>
> pass muster?

IANAL, but I would doubt if this could be construed as "fair use".
While it may be acceptable, in certain circumstances, to reverse
engineer code for the purpose of achieving interoperability, this
really is no different from reading the original sources, with the
intent to pass privileged information to a competitor.

> The values are also available at:
>
> 
http://msdn.microsoft.com/library/en-us/termserv/termserv/wm_wtssession_chan
ge.asp?frame=true


Ok.  This much, we can use then.

> The coding for the window message is still missing though.

So, unless you can find it publicly documented elsewhere, or you
can demonstrate a method for determining it *without* resort to the
SDK, them we must exclude it.

>>> Microsoft has protected these with a _WIN32_WINNT >= 0x0501,
>>> so we perhaps do the same.
>>
>> Again, how do you know this?  Unless they state it publicly, on
>> MSDN say, then we DON'T know that, and we can't make any such
>> assumption.
>
>  From MSDN:
>
> Client                 Requires Windows Vista or Windows XP.
> Server                 Requires Windows Server "Longhorn" or Windows 
Server 2003.

And these can be converted to the appropriate _WIN32_WINNT define
on the basis of publicly accessible information published here:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winprog/win
prog/using_the_windows_headers.asp
so we can also use that.

Please submit a patch:
http://www.mingw.org/MinGWiki/index.php/SubmitPatches

Cite the two MSDN references above as your sources, and include
only those defines which are actually documented there.

Thanks,
Keith.


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
MinGW-users mailing list
Min...@li...

You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users