2009/9/26 björn: > 2009/9/26 Kazuki Sakamoto: >> >> By the way, in my experience, >> "a combination of MacVim i386 and Vim x86_64" seems ok. > > Oh no! Don't do this! Due to my complete non-experience with 64 bit > I have managed to screw up the usage of variable widths -- some > messages have structures like this: > > long var1 > int var2 > > If this is passed from 64 bit Vim to 32 bit MacVim things will go > "kaboom" (or something less severe). > > This is the reason I forced the -m32 flag when building the Vim > binary. I will fix this properly when I get the time.
I fixed this problem now, so it should be safe to have Vim 64 bit and MacVim 32 bit (not that you'd want to anyway, but that's no reason not to fix this problem). At the same time I tried compiling MacVim 64 bit -- it is possible to get it to compile but you have to go into the Xcode project files and force it to compile 64 bit (both for MacVim and PSMTabBarControl). Beware though: there are masses of warnings, some are really problems that I need to fix too. Some observations regarding 64 bit MacVim: 1. File sizes in 64 bit: -rwxr-xr-x 1 winckler staff 613928 Sep 27 21:57 MacVim -rwxr-xr-x 1 winckler staff 2475280 Sep 27 21:57 Vim ... and 32 bit: -rwxr-xr-x 1 winckler staff 334344 Sep 2 14:31 MacVim -rwxr-xr-x 1 winckler staff 2083056 Sep 2 14:31 Vim Seems the MacVim binary almost _doubles_ in size! (Why?) 2. Memory usage in Activity Monitor shows me that a newly started 64 bit MacVim uses 12.4 Mb, 32 bit uses 9.1 Mb (although these numbers do tend to change so I wouldn't take this too seriously). Björn --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_mac" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
