Menu->strings[MENU_INDEX_TIP]);
+ msg_outtrans(pMenu->strings[MENU_INDEX_TIP]);
setcursor();
out_flush();
did_menu_tip = TRUE;
This patch seems to have solved my problem, and I have not found any
side-effects so far. Thanks!
Best re
y know the
limitations of these functions and always live within them when MSVC
is encountered.
Do we have any conclusions? It looks to me having /nodefaultlib:msvcrt
is still better then not having it.
Best regards,
Yongwei
--
Wu Yongwei
URL: http://wyw.dcweb.cn/
MSVCR71.dll removed _ctype, ??_E__non_rtti_object@@[EMAIL PROTECTED],
??_Ebad_cast@@[EMAIL PROTECTED], etc., but added ?swprintf@@YAHPAGIPBGZZ,
_CRT_RTC_INIT, __buffer_overrun, __pwctype_func, and so on.
Best regards,
Yongwei
--
Wu Yongwei
URL: http://wyw.dcweb.cn/
sults instead of evil ones using
it in building Vim.
-Original Message-
From: Yongwei Wu [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 17, 2007 7:15 AM
To: Doug Cook
Cc: Bram Moolenaar; Vim-dev mailing list
Subject: Re: MSVC build option about default library MSVCRT
Hi Doug,
On 17/05/07,
s. Linking with
MSVCRT.LIB in MSVC 7.1 results in the dependency on MSVCR71.DLL
instead of MSVCRT.DLL. This is not something we like, I suppose.
Best regards,
Yongwei
--
Wu Yongwei
URL: http://wyw.dcweb.cn/
ssary: in fact, then the option does not
have any effect at all.
I did actually try executing simple commands in Perl, Python, Tcl, and
Ruby, and they all succeeded.
I use the popular ActiveState builds for Perl, Python, and Tcl, and
ruby185-21 from the Ruby web site. I believe they are all MSVC
compatible.
Best regards,
Yongwei
--
Wu Yongwei
URL: http://wyw.dcweb.cn/
