Ben Fritz wrote:
But this is Windows. There is no "shadow" target in either the MinGW makefile, or the Visual Studio;
Don't the shadow dirs just create a real dir copy and use hard links for
the files (or do they use symlinks). Eitherway, Windows NT supports
hard links going back to win2k, and symlinks in vista or above. Might
just be a matter of the tools not taking advantage of the platform's
abilities.
Tony Mechelynck wrote:
What about building 32-bit Vim executables, like Mozilla does for
Firefox, Thunderbird and SeaMonkey? AFAIK, they run on both 32- and
64-bit Windows operating systems. Of course they cannot edit files
longer than 2 GiB (per file) but I don't expect that to be much of a
limitation.
----
Hey, Tony, 640K is more than enough for anyone's need, Bill G. said so!
When you are editing a large file, it is nice not to spill to tmp
files, not to mention 64-bit native on 64-bit runs about 10-15% faster
32-bit FF and others pay about 3-levels or more of stack redirection to
catch all the alignment problems and that's not counting double the time
for memory fetching unaligned words...(memory has big startup cost +
smaller/word, unaligned = 2 big startups).
--
--
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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_use+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
