This is the mail archive of the cygwin-developers@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: GetConsoleWindow


Corinna Vinschen wrote:
> 
> 
> If your intend is to follow the way practiced at MS, you have to
> set WINVER always to the most recent Windows version.  To compile
> explicitely for older platforms requires to set that value by hand.
> It's not the other way around.
>

Well, yes, but for w32api that would not be logical.  At least this
thread has pointed some doco weaknesses that I need to address.  Yes, if
you want to use the newer API functions then you must be aware to set
WINVER to the version you wish to support.  MS must do this for each
generation of new compilers to support newer OS's.  If give the
developer the freedom to not think about backward compatibility, and as
evidenced there is little.  We are smarter than that, so we choose to
let the developer set the version h[im|er]self, I.E.: the developer is
forced to think about the new functionality w.r.t. backward
compatibility of older OS versions.
 

> each other.  Anyway, the way to go should be:
> 
> - Your patch to guard GetCosoleWindow() was correct.
> 

I'm glad to see we agree here.

> - Set WINVER to 0x0500 if w32api doesn't define any XP/.NET-only
> functions/datatypes, to 0x0510 (or is it 0x0501?) otherwise.
> 

That is a Cygwin specific change.  If you wish to use functions
supported by 0x0500 then Cygwin must specifically redefine the WINVER
constant.

> - Fix the commdlg.h/unknwn.h problem.
> 

I'll have to look further into this one.

Earnie.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]