summaryrefslogtreecommitdiffstats
path: root/src/eval.c
AgeCommit message (Collapse)Author
2022-01-26patch 8.2.4226: filter-map test failsv8.2.4226Bram Moolenaar
Problem: Filter-map test fails. Solution: Only reject number argument in Vim9 script.
2022-01-26patch 8.2.4224: Vim9: no error when using a number for map() second argumentv8.2.4224Bram Moolenaar
Problem: Vim9: no error when using a number for map() second argument Solution: Disallow number to string conversion. (closes #9630)
2022-01-26patch 8.2.4223: long/int compiler warnings; function arguments swappedv8.2.4223K.Takata
Problem: Long/int compiler warnings; function arguments swapped. Solution: Add type casts. Swap arguments. (Ken Takata, closes #9632)
2022-01-24patch 8.2.4207: recursion test fails with MSVCv8.2.4207Bram Moolenaar
Problem: Recursion test fails with MSVC. Solution: Use a smaller limit for MSVC.
2022-01-24patch 8.2.4206: condition with many "(" causes a crashv8.2.4206Bram Moolenaar
Problem: Condition with many "(" causes a crash. Solution: Limit recursion to 1000.
2022-01-22patch 8.2.4179: 'foldtext' is evaluated in the current script contextv8.2.4179Bram Moolenaar
Problem: 'foldtext' is evaluated in the current script context. Solution: Use the script context where the option was set.
2022-01-21patch 8.2.4173: cannot use an import in 'foldexpr'v8.2.4173Bram Moolenaar
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.
2022-01-19patch 8.2.4145: confusing error when using name of import for a functionv8.2.4145Bram Moolenaar
Problem: Confusing error when using name of import for a function. Solution: Pass a flag to trans_function_name().
2022-01-18patch 8.2.4128: crash when method cannot be foundv8.2.4128Bram Moolenaar
Problem: Crash when method cannot be found. (Christian J. Robinson) Solution: Don't mix up pointer names.
2022-01-17patch 8.2.4125: completion tests failv8.2.4125Bram Moolenaar
Problem: Completion tests fail. Solution: Disable error messages while dereferencing the function name.
2022-01-17patch 8.2.4123: complete function cannot be import.Namev8.2.4123Bram Moolenaar
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)
2022-01-16patch 8.2.4117: Vim9: wrong white space error after using imported itemv8.2.4117Bram Moolenaar
Problem: Vim9: wrong white space error after using imported item. Solution: Don't skip over white space. (closes #9544)
2022-01-16patch 8.2.4115: cannot use a method with a complex expressionv8.2.4115Bram Moolenaar
Problem: Cannot use a method with a complex expression. Solution: Evaluate the expression after "->" and use the result.
2022-01-16patch 8.2.4110: Coverity warns for using NULL pointerv8.2.4110Bram Moolenaar
Problem: Coverity warns for using NULL pointer. Solution: Check "evalarg" is not NULL. Skip errors when "verbose" is false.
2022-01-15patch 8.2.4102: Vim9: import cannot be used after methodv8.2.4102Bram Moolenaar
Problem: Vim9: import cannot be used after method. Solution: Recognize an imported function name. (closes #9496)
2022-01-12patch 8.2.4069: Vim9: import test fails on MS-Windowsv8.2.4069Bram Moolenaar
Problem: Vim9: import test fails on MS-Windows. Solution: Ignore case. Adjust test to avoid name that only differs in case.
2022-01-09patch 8.2.4050: Vim9: need to prefix every item in an autoload scriptv8.2.4050Bram Moolenaar
Problem: Vim9: need to prefix every item in an autoload script. Solution: First step in supporting "vim9script autoload" and "import autoload".
2022-01-08patch 8.2.4043: using int for second argument of ga_init2()v8.2.4043Bram Moolenaar
Problem: Using int for second argument of ga_init2(). Solution: Remove unnessary type cast (int) when using sizeof().
2022-01-08patch 8.2.4038: various code not used when features are disabledv8.2.4038Dominique Pelle
Problem: Various code not used when features are disabled. Solution: Add #ifdefs. (Dominique Pellé, closes #9491)
2022-01-07patch 8.2.4024: confusing error message if imported name is used directlyv8.2.4024Bram Moolenaar
Problem: Confusing error message if imported name is used directly. Solution: Give a better error message.
2022-01-06patch 8.2.4019: Vim9: import mechanism is too complicatedv8.2.4019Bram Moolenaar
Problem: Vim9: import mechanism is too complicated. Solution: Do not use the Javascript mechanism but a much simpler one.
2022-01-05patch 8.2.4006: Vim9: crash when declaring variable on the command linev8.2.4006Bram Moolenaar
Problem: Vim9: crash when declaring variable on the command line. Solution: Use a temporary type list. (closes #9474)
2022-01-04patch 8.2.4005: error messages are spread outv8.2.4005Bram Moolenaar
Problem: Error messages are spread out. Solution: Move more error messages to errors.h.
2022-01-03patch 8.2.3991: Vim9: error when extending dict<any>v8.2.3991Bram Moolenaar
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)
2022-01-01patch 8.2.3977: error messages are spread outv8.2.3977Bram Moolenaar
Problem: Error messages are spread out. Solution: Move more error messages to errors.h.
2022-01-01patch 8.2.3972: error messages are spread outv8.2.3972Bram Moolenaar
Problem: Error messages are spread out. Solution: Move the last errors from globals.h to errors.h.
2022-01-01patch 8.2.3970: error messages are spread outv8.2.3970Bram Moolenaar
Problem: Error messages are spread out. Solution: Move more errors to errors.h.
2022-01-01patch 8.2.3967: error messages are spread outv8.2.3967Bram Moolenaar
Problem: Error messages are spread out. Solution: Move more errors to errors.h.
2021-12-31patch 8.2.3961: error messages are spread outv8.2.3961Bram Moolenaar
Problem: Error messages are spread out. Solution: Move more errors to errors.h.
2021-12-27patch 8.2.3916: no error for passing an invalid line number to append()v8.2.3916Bram Moolenaar
Problem: No error for passing an invalid line number to append(). Solution: In Vim9 script check for a non-negative number. (closes #9417)
2021-12-19patch 8.2.3852: Vim9: not enough testsv8.2.3852Bram Moolenaar
Problem: Vim9: not enough tests. Solution: Also run existing tests for Vim9 script. Make errors more consistent.
2021-12-19patch 8.2.3850: illegal memory access when displaying a partialv8.2.3850Bram Moolenaar
Problem: Illegal memory access when displaying a partial. Solution: Terminate the string with a NUL. (closes #9371)
2021-12-18patch 8.2.3847: illegal memory access when using a lambda with an errorv8.2.3847Bram Moolenaar
Problem: Illegal memory access when using a lambda with an error. Solution: Avoid skipping over the NUL after a string.
2021-12-17patch 8.2.3836: Vim9: comment after expression not skipped to find NLv8.2.3836Bram Moolenaar
Problem: Vim9: comment after expression not skipped to find NL. Solution: After evaluating an expression look for a newline after a # comment.
2021-12-16patch 8.2.3830: error messages are spread outv8.2.3830Bram Moolenaar
Problem: Error messages are spread out. Solution: Move more error messages to errors.h.
2021-12-15patch 8.2.3815: Vim9: cannot have a multi-line dict inside a blockv8.2.3815Bram Moolenaar
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.
2021-12-14patch 8.2.3810: Vim9: expr4 test fails on MS-Windowsv8.2.3810Bram Moolenaar
Problem: Vim9: expr4 test fails on MS-Windows. Solution: Do not give an error for a missing function name when skipping.
2021-12-14patch 8.2.3809: Vim9: crash when garbage collecting a nested partialv8.2.3809Bram Moolenaar
Problem: Vim9: crash when garbage collecting a nested partial. (Virginia Senioria) Solution: Set references in all the funcstacks. (closes #9348)
2021-12-14patch 8.2.3807: Vim9: can call import with star directlyv8.2.3807Bram Moolenaar
Problem: Vim9: can call import with star directly. Solution: Check that the import used star.
2021-12-13patch 8.2.3796: the funcexe_T struct members are not named consistentlyv8.2.3796Bram Moolenaar
Problem: The funcexe_T struct members are not named consistently. Solution: Prefix "fe_" to all the members.
2021-12-12patch 8.2.3788: lambda for option that is a function may be freedv8.2.3788Yegappan Lakshmanan
Problem: Lambda for option that is a function may be garbage collected. Solution: Set a reference in the funcref. (Yegappan Lakshmanan, closes #9330)
2021-12-11patch 8.2.3783: confusing error for using a variable as a functionv8.2.3783Bram Moolenaar
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)
2021-12-09patch 8.2.3767: crash when using NULL partialv8.2.3767Bram Moolenaar
Problem: Crash when using NULL partial. Solution: Check for NULL.
2021-12-09patch 8.2.3766: converting a funcref to a string leaves out "g:"v8.2.3766Bram Moolenaar
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.
2021-12-06patch 8.2.3751: cannot assign a lambda to an option that takes a functionv8.2.3751Yegappan Lakshmanan
Problem: Cannot assign a lambda to an option that takes a function. Solution: Automatically convert the lambda to a string. (Yegappan Lakshmanan, closes #9286)
2021-11-29patch 8.2.3695: confusing error for missing keyv8.2.3695Bram Moolenaar
Problem: Confusing error for missing key. Solution: Use the actualy key for the error. (closes #9241)
2021-11-22patch 8.2.3650: Vim9: for loop variable can be a list memberv8.2.3650Bram Moolenaar
Problem: Vim9: for loop variable can be a list member. Solution: Check for valid variable name. (closes #9179)
2021-10-23patch 8.2.3560: using freed memory with lambdav8.2.3560Bram Moolenaar
Problem: Using freed memory with lambda. Solution: Do not free lines early, keep them until the expression is finished.
2021-09-09patch 8.2.3418: garbage collection while evaluating may cause troublev8.2.3418Christian Brabandt
Problem: Garbage collection while evaluating may cause trouble. Solution: Disable garbage collection while evaluating an expression. (Christian Brabandt, issue #8848)
2021-08-23patch 8.2.3370: Vim9: no check for white space before type in declarationv8.2.3370Bram Moolenaar
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)