2010/7/27 Andreas Jellinghaus <[email protected]>:
> but maybe investing work here isn't worth the hassle. people have written
> apps using "DWORD" in their code to access pcsc-lite, so we would still
> need to define "DWORD" in pcsc-lite headers as 64bit data type, even if
> it confuses people. not doing so would break the compilation of such apps.
Do you think some people are knowingly using DWORD to be a 64-bits integer?
And then redefining DWORD to be 32-bits would break their application.
> you could write a new header file, or use a define inside the old ones,
> so people could switch from "DWORD" to some new name for the same type,
> some name that reflects the "64 bit on 64 bit systems" situation better.
> but who would migrate their app, why and when?
Mac OS X uses uint32_t and normal C types like in:
PCSC_API int32_t SCardConnect(SCARDCONTEXT hContext,
const char *szReader,
uint32_t dwShareMode,
uint32_t dwPreferredProtocols,
LPSCARDHANDLE phCard, uint32_t *pdwActiveProtocol);
The PC/SC (and pcsc-lite) API uses DWORD and such Windows types
everywhere. I do not plan to change that but that would be also a very
good idea. Windows types are so unreadable (for me).
PCSC_API LONG SCardConnect(SCARDCONTEXT hContext,
LPCSTR szReader,
DWORD dwShareMode,
DWORD dwPreferredProtocols,
LPSCARDHANDLE phCard, LPDWORD pdwActiveProtocol);
Bye
--
Dr. Ludovic Rousseau
_______________________________________________
Muscle mailing list
[email protected]
http://lists.drizzle.com/mailman/listinfo/muscle
