Bram wrote: > And how do we make this work on older systems and older compilers?
Well it is only an issue when using the 32-bit Vim on 64-bit Windows, and the API is available on all 64-bit Windows versions (XP64 and later). To have the same 32-bit Vim binary be maximally portable to even older versions of Windows, the best bet is to use LoadLibrary()/GetProcAddress() as is done elsewhere in Vim. The choice of compiler shouldn't be an issue. Of course if we had a "official" native 64-bit Windows compile of Vim, not only would the above problem not exist, but we'd also be able to edit huge-*** files. :) It's time IMO. 64-bit is becoming ubiquitous. --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
