[PD] [comport] for windows

Winfried Ritsch ritsch at iem.at
Sat Oct 29 14:22:22 CEST 2005


Hello,

> >
> >for WINDOWS 2000 i had a #ifdef WIN2000 in my code which wasnt in CVS, i
> > just committed now. This  means the    FILE_FLAG_OVERLAPPED at open is
> > not used. I never  found out why but then WINDOWS2000 worked,
>
> i have no insight into the comport external but a #define WIN2000 seems
> odd to me.
[...]

You are right. I used a definition which is not official because the code 
should be never used except on some windows2000 computer where we dont know 
why this is needed. So I used this trick just to get some more testing and 
input to fix this issue more seriously, not breaking other compilations and 
then this define will be removed. It should not be used by default even for 
windows2000 machines. Maybe i should rename it to BUGWIN2000 or so.


mfg winfried

> To differentiate between Windows and linux there are other preprocessor
> defines like _WIN32 which should be defined for every Windows-based
> compiler (or __linux__ respectively).
> To make a compilation specific for different Windows versions, like
> Win95, 2000, XP the preprocessor definitions WINVER and _WIN32_WINNT
> should be used (see
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winprog/wi
>nprog/using_the_windows_headers.asp) which also let the respective Windows
> API functions be included.
> There are other available definitions for MacOS (9/X CFM/MachO) and linux.
>
> It would be great if the PD (as already motivated by James Tittle, as i
> think to recall) and external sources could use these symbols for
> automatic configuration.
>
> best greetings,
> Thomas




More information about the Pd-list mailing list