aboutsummaryrefslogtreecommitdiff
path: root/src/nvim/viml/parser/expressions.c
Commit message (Collapse)AuthorAge
* Refactor/uncrustify (#15790)dundargoc2021-09-29
| | | | | | | | | | | | | * refactor: format with uncrustify * fixup(dundar): fix functions comments * fixup(dundar): remove space between variable and ++/-- * fixup(dundar): better workaround for macro attributes This is done to be able to better use uncrustify rules for macros * fixup(justin): make preprocessors follow neovim style guide
* refactor: format #15702dundargoc2021-09-18
|
* fix(typo): overriden -> overridden (RE: PR #14159) (#15360)Oliver Marriott2021-09-17
|
* vim-patch:8.1.1355: obvious mistakes are accepted as valid expressionsSean Dewar2021-09-11
| | | | | | | | | Problem: Obvious mistakes are accepted as valid expressions. Solution: Be more strict about parsing numbers. (Yasuhiro Matsumoto, closes vim/vim#3981) https://github.com/vim/vim/commit/16e9b85113e0b354ece1cb4f5fcc7866850f3685 Update vim_str2nr_spec.lua to add more tests that use strict = true.
* Use abort() instead of assert(false) for things that should never happenJames McCoy2021-01-31
| | | | | | | | assert() is compiled out for release builds, but we don't want to continue running in these impossible situations. This also resolves the "implicit fallthrough" warnings for the asserts in switch cases.
* robustness: avoid adding offset to NULL pointerBjörn Linse2020-09-04
| | | | | | | | | | | UBSAN with clang 10.0 is checking for adding offsets to a `NULL` pointer which is not allowed. This is not yet checked in the version of clang used in CI (7.0.0). I will work on cases of this so that tests passes locally for me. This could be tested in CI by either upgrading the clang of the ASAN/UBSAN to 10.0, or add yet another CI target which builds with clang 10.0.
* Removed redundant defineJakub Łuczyński2020-02-13
|
* clang/"dead assignments" #10620Bartosz Miera2019-07-29
| | | | Also revert possibly-wrong change in f_sign_getplaced() from 652be3cb0040.
* PVS/V547: viml/parser/expressions.c: Expression is always trueJustin M. Keyes2019-01-04
|
* Merge #8218 'Fix errors reported by PVS'Justin M. Keyes2018-04-27
|\ | | | | closes #4983
| * viml/parser/expressions: Fix PVS/V547: condition checked earlierZyX2018-04-15
| | | | | | See previous goto with the same label.
| * viml/parser/expressions: Fix PVS/V547: condition checked earlierZyX2018-04-15
| | | | | | See previous goto with the same label.
* | build/clang 6.0.0: fix type conversion warnings (#8235)Marco Hinz2018-04-07
|/
* *: Replace all occurrences of NVim with NvimZyX2017-11-30
|
* keymap: Do not use vim_isIDc in keymap.cZyX2017-11-30
| | | | | | | | Note: there are three changes to ascii_isident. Reverting first two (in find_special_key and first in get_special_key_code) normally fails the new test with empty &isident, but reverting the third does not. Hence adding `>` to &isident. Ref vim/vim#2389.
* viml/parser/expressions: Make sure that listed nodes may be presentZyX2017-11-26
| | | | With the new test leaving `assert(false);` for any of the cases makes tests crash.
* viml/parser/expressions: Make $ENV not depend on &isidentZyX2017-11-26
|
* *: Fix linter errorsZyX2017-11-19
|
* viml/parser/expressions,unittests: Do better testing, fix found issuesZyX2017-11-19
|
* unittests,viml/parser/expressions: Start adding asgn parsing testsZyX2017-11-13
|
* unittests: Add some more edge test casesZyX2017-11-12
|
* viml/parser/expressions: Add support for parsing assignmentsZyX2017-11-12
|
* viml/parser/expressions: Replace lambda-specific WantedNode entriesZyX2017-11-12
| | | | | This way code will be easier to adapt to handling (partially) non-expressions like :let lvalue part or :function definitions, and that would be needed in the future both for proper completion support and for the Ex commands parser.
* *: Fix linter errorsZyX2017-11-06
|
* viml/parser/expressions: Briefly document some differencesZyX2017-11-06
|
* api/vim,functests: Add tests for nvim_parse_expression, fix found bugsZyX2017-11-06
|
* vim/api: Actually dump AST, fix some bugs in nvim_parse_expressionZyX2017-11-06
|
* *: Fix linter errorsZyX2017-10-30
| | | | Big function in expressions.c may be refactored, if I ever catch the idea how to split it right.
* syntax,viml/parser/expressions: Add missing highlight groupsZyX2017-10-29
| | | Also adjusts some names.
* syntax,viml/expressions/parser: Create defaults for expr highlightingZyX2017-10-29
|
* api/vim: Add nvim_parse_expression functionZyX2017-10-29
|
* viml/parser/expressions: Fix last error found by KLEEZyX2017-10-29
|
* viml/parser/expressions: Fix some errors spotted by KLEEZyX2017-10-19
| | | Not all of them are fixed yet though.
* viml/parser/expressions: Add some castsZyX2017-10-16
|
* viml/parser/expressions: Fix memory leak when processing ternaryZyX2017-10-16
|
* viml/parser/expressions: Highlight prefix separately from numberZyX2017-10-16
| | | Should make accidental octals more visible.
* viml/parser/expressions: Define east_node_type_tab only when neededZyX2017-10-15
|
* viml/parser/expressions: Update some comments and add another checkZyX2017-10-15
|
* viml/parser/expressions,tests: Add AST freeing, with sanity checksZyX2017-10-15
|
* viml/parser/expressions: Create tests for latest additionsZyX2017-10-15
|
* viml/parser/expressions: Finish parserZyX2017-10-15
| | | | | | | Note: formatc.lua was unable to swallow some newer additions to ExprASTNodeType (specifically `kExprNodeOr = '|'` and probably something else), so all `= …` were dropped: in any case they only were there in order to not bother updating viml_pexpr_debug_print_ast_node and since it is now known all nodes which will be present it is not much of an issue.
* viml/parser/expressions: Add support for string parsingZyX2017-10-15
|
* viml/parser/expressions: Add support for subscript and list literalsZyX2017-10-15
|
* viml/parser/expressions: Error out on multiple colons in a rowZyX2017-10-15
|
* viml/parser/expressions: Add support for the dot operator and numbersZyX2017-10-15
|
* viml/parser/expressions: Make lexer parse numbers, support non-decimalZyX2017-10-15
|
* viml/parser/expressions: Forbid dot or alpha characters after a floatZyX2017-10-15
| | | | | This is basically what Vim already does, in addition to forbidding floats should there be a concat immediately before it.
* viml/parser/expressions: Add support for comparison operatorsZyX2017-10-15
|
* viml/parser/expressions: Make sure that arrows outside lambda throwZyX2017-10-15
|
* viml/parser/expressions: Add support for ternary operatorZyX2017-10-15
|
generated by cgit (git 2.34.1) at 2025-05-11 22:54:33 +0000