Age | Commit message (Collapse) | Author |
|
Problem: Filter-map test fails.
Solution: Only reject number argument in Vim9 script.
|
|
Problem: Vim9: no error when using a number for map() second argument
Solution: Disallow number to string conversion. (closes #9630)
|
|
Problem: Long/int compiler warnings; function arguments swapped.
Solution: Add type casts. Swap arguments. (Ken Takata, closes #9632)
|
|
Problem: Recursion test fails with MSVC.
Solution: Use a smaller limit for MSVC.
|
|
Problem: Condition with many "(" causes a crash.
Solution: Limit recursion to 1000.
|
|
Problem: 'foldtext' is evaluated in the current script context.
Solution: Use the script context where the option was set.
|
|
Problem: Cannot use an import in 'foldexpr'.
Solution: Set the script context to where 'foldexpr' was set. (closes #9584)
Fix that the script context was not set for all buffers.
|
|
Problem: Confusing error when using name of import for a function.
Solution: Pass a flag to trans_function_name().
|
|
Problem: Crash when method cannot be found. (Christian J. Robinson)
Solution: Don't mix up pointer names.
|
|
Problem: Completion tests fail.
Solution: Disable error messages while dereferencing the function name.
|
|
Problem: Complete function cannot be import.Name.
Solution: Dereference the function name if needed. Also: do not see
"import.Name" as a builtin function. (closes #9541)
|
|
Problem: Vim9: wrong white space error after using imported item.
Solution: Don't skip over white space. (closes #9544)
|
|
Problem: Cannot use a method with a complex expression.
Solution: Evaluate the expression after "->" and use the result.
|
|
Problem: Coverity warns for using NULL pointer.
Solution: Check "evalarg" is not NULL. Skip errors when "verbose" is false.
|
|
Problem: Vim9: import cannot be used after method.
Solution: Recognize an imported function name. (closes #9496)
|
|
Problem: Vim9: import test fails on MS-Windows.
Solution: Ignore case. Adjust test to avoid name that only differs in case.
|
|
Problem: Vim9: need to prefix every item in an autoload script.
Solution: First step in supporting "vim9script autoload" and "import
autoload".
|
|
Problem: Using int for second argument of ga_init2().
Solution: Remove unnessary type cast (int) when using sizeof().
|
|
Problem: Various code not used when features are disabled.
Solution: Add #ifdefs. (Dominique Pellé, closes #9491)
|
|
Problem: Confusing error message if imported name is used directly.
Solution: Give a better error message.
|
|
Problem: Vim9: import mechanism is too complicated.
Solution: Do not use the Javascript mechanism but a much simpler one.
|
|
Problem: Vim9: crash when declaring variable on the command line.
Solution: Use a temporary type list. (closes #9474)
|
|
Problem: Error messages are spread out.
Solution: Move more error messages to errors.h.
|
|
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 error messages to errors.h.
|
|
Problem: Error messages are spread out.
Solution: Move the last errors from globals.h to errors.h.
|
|
Problem: Error messages are spread out.
Solution: Move more errors to errors.h.
|
|
Problem: Error messages are spread out.
Solution: Move more errors to errors.h.
|
|
Problem: Error messages are spread out.
Solution: Move more errors to errors.h.
|
|
Problem: No error for passing an invalid line number to append().
Solution: In Vim9 script check for a non-negative number. (closes #9417)
|
|
Problem: Vim9: not enough tests.
Solution: Also run existing tests for Vim9 script. Make errors more
consistent.
|
|
Problem: Illegal memory access when displaying a partial.
Solution: Terminate the string with a NUL. (closes #9371)
|
|
Problem: Illegal memory access when using a lambda with an error.
Solution: Avoid skipping over the NUL after a string.
|
|
Problem: Vim9: comment after expression not skipped to find NL.
Solution: After evaluating an expression look for a newline after a #
comment.
|
|
Problem: Error messages are spread out.
Solution: Move more error messages to errors.h.
|
|
Problem: Vim9: cannot have a multi-line dict inside a block.
Solution: Do not split the command at a line break, handle NL characters
as white space.
|
|
Problem: Vim9: expr4 test fails on MS-Windows.
Solution: Do not give an error for a missing function name when skipping.
|
|
Problem: Vim9: crash when garbage collecting a nested partial. (Virginia
Senioria)
Solution: Set references in all the funcstacks. (closes #9348)
|
|
Problem: Vim9: can call import with star directly.
Solution: Check that the import used star.
|
|
Problem: The funcexe_T struct members are not named consistently.
Solution: Prefix "fe_" to all the members.
|
|
Problem: Lambda for option that is a function may be garbage collected.
Solution: Set a reference in the funcref. (Yegappan Lakshmanan,
closes #9330)
|
|
Problem: Confusing error for using a variable as a function.
Solution: If a function is not found but there is a variable, give a more
useful error. (issue #9310)
|
|
Problem: Crash when using NULL partial.
Solution: Check for NULL.
|
|
Problem: Converting a funcref to a string leaves out "g:", causing the
meaning of the name depending on the context.
Solution: Prepend "g:" for a global function.
|
|
Problem: Cannot assign a lambda to an option that takes a function.
Solution: Automatically convert the lambda to a string. (Yegappan
Lakshmanan, closes #9286)
|
|
Problem: Confusing error for missing key.
Solution: Use the actualy key for the error. (closes #9241)
|
|
Problem: Vim9: for loop variable can be a list member.
Solution: Check for valid variable name. (closes #9179)
|
|
Problem: Using freed memory with lambda.
Solution: Do not free lines early, keep them until the expression is
finished.
|
|
Problem: Garbage collection while evaluating may cause trouble.
Solution: Disable garbage collection while evaluating an expression.
(Christian Brabandt, issue #8848)
|
|
Problem: Vim9: no check for white space before type in declaration.
(Naohiro Ono)
Solution: Check for white space like in a compiled function. (closes #8785)
|