aboutsummaryrefslogtreecommitdiff
path: root/src/nvim/viml/parser
Commit message (Collapse)AuthorAge
...
* refactor: format header files with uncrustify #15877dundargoc2021-10-09
| | | | | | * refactor: format header files with uncrustify * fixup(justin): skip formatting of terminfo_defs.h * fixup: force winsock2 to be included first * fixup: simplify disable/enable directive to "uncrustify:off/on"
* 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.
* Merge #11851 'eval.c: factor out eval/userfunc.c'Justin M. Keyes2020-04-26
|\ | | | | | | vim-patch:7.4.2058
| * Removed redundant defineJakub Łuczyński2020-02-13
| |
* | nvim:viml: Fix enum declaration of ExprParserFlagsAndreas Schneider2020-02-23
|/ | | | | | | | | | | Instead of declaring an enum, this creates a global variable. As gcc10 uses -fno-common by default, global variables declared with the same name more than once is not allowed anymore revealing this issue. Each time this header is included, we define the enum name as a global variable. See also https://bugzilla.redhat.com/show_bug.cgi?id=1799680
* 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
|/
* Add missing PVS headers to new filesJames McCoy2018-03-11
|
* *: 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
|
* ex_getln: Make use of new parser to color expressionsZyX2017-10-29
| | | Retires g:Nvim_color_expr callback.
* 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: Remove unused flagZyX2017-10-16
|
* viml/parser/expressions: Fix memory leak when processing ternaryZyX2017-10-16
|
* klee: Include colors in testZyX2017-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,klee: Fix some problems found by KLEE runZyX2017-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
|
generated by cgit (git 2.34.1) at 2025-04-29 04:45:16 +0000