It's not that "many programmers still refer to Windows API as Win32", it's that the Windows API itself has decided that that is what it is called. When you #define _WIN32 in a C or C++ program using the Windows API, it does not mean "this is a 32-bit app", it means "I'm using the Windows API". That's why you still define this even in 64-bit builds, for example, where you #define both _WIN32 and _WIN64.
You're not wrong, but it's just that the problem goes deeper than what you make it sound :) The Windows API *is* the Win32 API and vice versa. They are synonyms. On Sun, Oct 25, 2015 at 11:24 PM eryksun <eryk...@gmail.com> wrote: > On 10/25/15, Laura Creighton <l...@openend.se> wrote: > > > > Can I suggest a mailing list name change to reflect 64 bit windows? > > python-windows would be my suggestion .... > > I agree. This list is about programming in Python on Windows, so > python-windows is an obvious name and one that a novice programmer can > easily recognize. > > I think the name has yet to change because a lot of programmers still > refer to the Windows API as "Win32" instead of "WinAPI". Also, the > system directory on 64-bit Windows is still called "System32", and > many of the more well-known system DLLs still have "32" in the name, > such as the following: > > shell32, ole32, kernel32, crypt32, opengl32, > user32, advapi32, win32spl, comctl32, comdlg32, > gdi32, rasapi32, w32time, wldap32, ws2_32, > tapi32, cfgmgr32, imm32, msvfw32, clfsw32, > netapi32, wtsapi32, mssign32, secur32, riched32 > _______________________________________________ > python-win32 mailing list > python-win32@python.org > https://mail.python.org/mailman/listinfo/python-win32 >
_______________________________________________ python-win32 mailing list python-win32@python.org https://mail.python.org/mailman/listinfo/python-win32
