On 17-Sep-2020 05:08, Bram Moolenaar wrote:
Patch 8.2.1698
Problem: Cannot lock a variable in legacy Vim script like in Vim9.
Solution: Make ":lockvar 0" work.
Files: runtime/doc/eval.txt, src/evalvars.c, src/proto/evalvars.pro,
src/dict.c, src/eval.c, src/list.c, src/typval.c, src/userfunc.c,
src/testdir/test_const.vim, src/testdir/test_listdict.vim
After this patch, mingw64 (gcc 10.2) spits out this error:
<snip>
gcc -c -I. -Iproto -DWIN32 -DWINVER=0x0603 -D_WIN32_WINNT=0x0603
-DHAVE_PATHDEF -DFEAT_NORMAL -DHAVE_STDINT_H -pipe -march=native -Wall
-O3 -fomit-frame-pointer -freg-struct-return -fpie -fPIE
-DFEAT_GUI_MSWIN -DFEAT_CLIPBOARD -D__USE_MINGW_ANSI_STDIO evalvars.c -o
gobjnative/evalvars.o
In file included from evalvars.c:14:
evalvars.c: In function 'var_check_lock':
evalvars.c:3176:10: error: 'e_variable_is_locked_str' undeclared (first
use in this function); did you mean 'e_variable_not_found_str'?
3176 | semsg(_(e_variable_is_locked_str),
| ^~~~~~~~~~~~~~~~~~~~~~~~
vim.h:548:25: note: in definition of macro '_'
548 | # define _(x) ((char *)(x))
| ^
evalvars.c:3176:10: note: each undeclared identifier is reported only
once for each function it appears in
3176 | semsg(_(e_variable_is_locked_str),
| ^~~~~~~~~~~~~~~~~~~~~~~~
vim.h:548:25: note: in definition of macro '_'
548 | # define _(x) ((char *)(x))
| ^
make: *** [Make_cyg_ming.mak:1139: gobjnative/evalvars.o] Error 1
</snip>
It would seem we are missing an error message (e_variable_is_locked_str).
Cheers
John
--
--
You received this message from the "vim_dev" 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_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_dev/7c38a014-992e-ff5d-1a76-7cb93a38d83e%40internode.on.net.
