| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Problem: Using sizeof() and subtract array size is tricky.
Solution: Use offsetof() instead. (closes #11926)
|
|
|
|
|
|
| |
Problem: Code is indented more than necessary.
Solution: Use an early return where it makes sense. (Yegappan Lakshmanan,
closes #11887)
|
|
|
|
|
| |
Problem: Cannot call an object method in a compiled function.
Solution: Compile the instructins to invoke an object method.
|
|
|
|
|
| |
Problem: Error message names do not match the items.
Solution: Add "_str" when the text contains "%s".
|
|
|
|
|
| |
Problem: Vim9 class is not implemented yet.
Solution: Add very basic class support.
|
|
|
|
|
|
| |
Problem: Crash when unletting a variable while listing variables.
Solution: Disallow changing a hashtable while going over the entries.
(closes #11435)
|
|
|
|
|
|
| |
Problem: "export def" does not work in a nested block.
Solution: Do not handle "export" with a separate function but in the same
command stack. (closes #11304)
|
|
|
|
|
| |
Problem: FORTIFY_SOURCE causes a crash in Vim9 script.
Solution: Use a pointer to the first char. (Yee Cheng Chin, closes #11302)
|
|
|
|
|
|
|
| |
Problem: A symlink to an autoload script results in two entries in the list
of scripts, items expected in one are actually in the other.
Solution: Have one script item refer to the actually sourced one.
(closes #10960)
|
|
|
|
|
| |
Problem: Cannot build with small features.
Solution: Check for E1170 only with FEAT_EVAL.
|
|
|
|
|
| |
Problem: Giving E1170 only in an expression is confusing.
Solution: Give E1170 for any "#{ comment". (closes #10855)
|
|
|
|
|
|
| |
Problem: Error for using #{ in an expression is a bit confusing.
Solution: Mention that this error is only given for an expression.
Avoid giving the error more than once. (closes #10855)
|
|
|
|
|
| |
Problem: Vim9: a few lines not covered by tests.
Solution: Add a few tests.
|
|
|
|
|
| |
Problem: Expression in command block does not look after NL.
Solution: Skip over NL to check what follows. (closes #10358)
|
|
|
|
|
| |
Problem: Setting ufunc to NULL twice.
Solution: Set ufunc to NULL in find_exported(). (closes #19275)
|
|
|
|
|
|
| |
Problem: Crash when imported autoload script was deleted.
Solution: Initialize local variable. (closes #10274) Give a more meaningful
error message.
|
|
|
|
|
| |
Problem: Error from setting an option is silently ignored.
Solution: Handle option value errors better. Fix uses of N_().
|
|
|
|
|
|
| |
Problem: Vim9: script variable has no flag that it was set.
Solution: Add a flag that it was set, to avoid giving it a value when used.
(closes #10088)
|
|
|
|
|
| |
Problem: Vim9: can use :unlockvar for const variable. (Ernie Rael)
Solution: Check whether the variable is a const.
|
|
|
|
|
|
|
| |
Problem: Vim9: can't use items from "import autoload" with autoload
directory name.
Solution: Let sn_autoload_prefix overrule sn_import_autoload.
(closes #10054)
|
|
|
|
|
| |
Problem: Missing changes for import check.
Solution: Add missing changes.
|
|
|
|
|
| |
Problem: "import autoload" only works with using 'runtimepath'.
Solution: Also support a relative and absolute file name.
|
|
|
|
|
|
| |
Problem: Vim9: in :def function script var cannot be null.
Solution: Only initialize a script variable when not set to a null value.
(closes #10034)
|
|
|
|
|
| |
Problem: Sourcing buffer lines may lead to errors for conflicts.
Solution: Add the ++clear argument. (Yegappan Lakshmanan, closes #9991)
|
|
|
|
|
|
| |
Problem: Need to write script to a file to be able to source them.
Solution: Make ":source" use lines from the current buffer. (Yegappan
Lakshmanan et al., closes #9967)
|
|
|
|
|
| |
Problem: Vim9: cannot set variables to a null value.
Solution: Add null_list, null_job, etc.
|
|
|
|
|
| |
Problem: ctx_imports is not used.
Solution: Delete ctx_imports. Add missing dependency.
|
|
|
|
|
| |
Problem: cstack not always passed to where it is needed.
Solution: Pass ctack through functions.
|
|
|
|
|
| |
Problem: Vim9: incomplete test for existing script variable in block.
Solution: Add a couple more tests. Fix uncovered problem.
|
|
|
|
|
| |
Problem: Vim9: no error if script imports itself.
Solution: Give an error when a script imports itself.
|
|
|
|
|
| |
Problem: Long/int compiler warnings; function arguments swapped.
Solution: Add type casts. Swap arguments. (Ken Takata, closes #9632)
|
|
|
|
|
|
| |
Problem: Vim9: calling import with and without method is inconsistent.
Solution: Set a flag that a parenthsis follows to compile_load_scriptvar().
Add some more tests. Improve error message.
|
|
|
|
|
| |
Problem: Vim9: the "autoload" argument of ":vim9script" is not useful.
Solution: Remove the argument. (closes #9555)
|
|
|
|
|
| |
Problem: MS-Windows: test for import with absolute path fails.
Solution: Handle path starting with slash as an absolute path.
|
|
|
|
|
| |
Problem: Vim9: wrong error message when autoload script can't be found.
Solution: Correct check for using autoload with wrong name.
|
|
|
|
|
| |
Problem: Cannot test items from an autoload script easily.
Solution: Add the "autoload" value for test_override().
|
|
|
|
|
| |
Problem: "cctx" argument of find_func_even_dead() is unused.
Solution: Remove the argument.
|
|
|
|
|
| |
Problem: Memory leak in autoload import.
Solution: Do not overwrite the autoload prefix.
|
|
|
|
|
|
| |
Problem: Vim9: compiling function fails when autoload script is not loaded
yet.
Solution: Depend on runtime loading.
|
|
|
|
|
| |
Problem: Vim9: imported autoload script loaded again.
Solution: Do not create a new imported_T every time.
|
|
|
|
|
| |
Problem: Vim9: not fully implementing the autoload mechanism.
Solution: Allow for exporting a legacy function. Improve test coverage.
|
|
|
|
|
|
|
| |
Problem: Vim9: autoload mechanism doesn't fully work yet.
Solution: Define functions and variables with their autoload name, add the
prefix when calling a function, find the variable in the table of
script variables.
|
|
|
|
|
|
| |
Problem: Vim9: need to prefix every item in an autoload script.
Solution: First step in supporting "vim9script autoload" and "import
autoload".
|
|
|
|
|
| |
Problem: Vim9: no error when importing the same script twice.
Solution: Give an error, unless it is a reload.
|
|
|
|
|
| |
Problem: Various code not used when features are disabled.
Solution: Add #ifdefs. (Dominique Pellé, closes #9491)
|
|
|
|
|
| |
Problem: Error for import not ending in .vim does not work for .vimrc.
Solution: Check that .vim is the end. (closes #9484)
|
|
|
|
|
| |
Problem: Using uninitialized variable.
Solution: Initialize "ufunc" also when an item is not exported.
|
|
|
|
|
| |
Problem: Vim9: import mechanism is too complicated.
Solution: Do not use the Javascript mechanism but a much simpler one.
|
|
|
|
|
|
|
| |
Problem: Vim9: error when extending dict<any> with another type that it was
initialized with.
Solution: Also set the type for dict<any> if the initializer has a more
specific type. (closes #9461)
|
|
|
|
|
| |
Problem: Error messages are spread out.
Solution: Move more errors to errors.h.
|