> George V. Reilly said:
>> I think a better solution would be a smarter Windows installer for Vim which included Win32 and Win64 copies of gvimext.dll and a Win32 gvim.exe, that installed the appropriate flavor of the shell extension DLL.
>
> There are still a few reasons why one might want a native 64-bit version of Vim:
> 1) Editing files> 4GB in size, rare I know, but still.
> 2) 64-bit WinPE does not have a WOW64 subsystem, hence you cannot run a 32-bit executable.
> 3) Windows Server 2008 R2 (i.e. Win7 Server) also does not have the WOW64 subsystem, by default, although it is an optional component you can install.
> 4) Potential for perf gains, particularly in heavy memory operations like memcpy and memcmp which can be optimized for the 64-bit word size.
>
> Those are in addition to the Explorer integration issue that you mention.
>
> I would definitely use the 64-bit Vim if it came in an official installer. As it is, I don't use your (George) 64-bit binary, just because I like to use the vanilla official binary.
>
> Craig
>
The "vanilla official binary" Vim for Windows (compiled by Bram) is a
7.2.000, and severely outdated by now. Even Steve Hall's "Vim without
Cream", though compiled from "official" sources and patches, is supposed
to be "unofficial". Yet IMHO it is still the best ready-made Vim
available for W32.
Best regards,
Tony.
--
GUARD #1: Where'd you get the coconut?
ARTHUR: We found them.
GUARD #1: Found them? In Mercea? The coconut's tropical!
ARTHUR: What do you mean?
GUARD #1: Well, this is a temperate zone.
The Quest for the Holy Grail (Monty
Python)
--
You received this message from the "vim_use" 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
Subscription settings: http://groups.google.com/group/vim_use/subscribe?hl=en
No comments:
Post a Comment