Ken Takata wrote:
> I thought that defining `WIN3264` was redundant, because it is exactly the > same as `_WIN32`. > However, one merit for using `WIN3264` is that it can avoid misunderstanding > that `_WIN32` doesn't includes `_WIN64` (which is incorrect). > `MSWIN` was used for both Win16 and Win32, but we have already dropped the > support for Win16. > So now `MSWIN`, `WIN3264` and `_WIN32` (and also `WIN32`) are all the same. > > Using `_WIN32` is a standard way in the Windows programming. So it is > straightforward. > However, still there's a risk that someone misunderstands that it doesn't > include `_WIN64`. Do we need to care such a case? If so, `MSWIN` might be > better. It is best to separate the dependency on the compiler and Makefile from what we use throughout Vim code. "MSWIN" is the easiest to understand for all builds on MS-Windows. Then we can define it in one place in vim.h, depending on _WIN32 or WIN32 (WIN32 is defined in all the MS-Windows makefiles). We can keep using _WIN64 for 64-bit specific code. -- A fool must search for a greater fool to find admiration. /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
