On 27-Jan-2020 05:29, Bram Moolenaar wrote:
Patch 8.2.0154
Problem: Reallocating the list of scripts is inefficient.
Solution: Instead of using a growarray of scriptitem_T, store pointers and
allocate each scriptitem_T separately. Also avoids that the
growarray pointers change when sourcing a new script.
Files: src/globals.h, src/eval.c, src/evalvars.c, src/ex_docmd.c,
src/profiler.c, src/scriptfile.c, src/vim9compile.c,
src/vim9execute.c, src/vim9script.c
After patches 8.20149 to 8.21054, mingw (gcc 9.2.1) throws a large
number of errors and warnings relating to the new vim9script code if
FEAT_FLOAT is not defined. The leads me to this question: will the
FEAT_FLOAT feature be required in vim from now on?
When I defined FEAT_FLOAT all the errors and all but one warning went
away. The remaining warning was this:
<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 vim9script.c -o
objnative/vim9script.o
vim9script.c: In function 'handle_import':
vim9script.c:378:28: warning: 'ufunc' may be used uninitialized in this
function [-Wmaybe-uninitialized]
378 | imported->imp_funcname = ufunc->uf_name;
| ^~~~~
vim9script.c:374:26: warning: 'sv' may be used uninitialized in this
function [-Wmaybe-uninitialized]
374 | imported->imp_type = sv->sv_type;
| ~~^~~~~~~~~
</snip>
Regards
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/245cf420-70aa-1db7-f728-3fa367be6535%40internode.on.net.
