aboutsummaryrefslogtreecommitdiff
path: root/src/nvim/viml/parser/expressions.c
Commit message (Collapse)AuthorAge
...
* | 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
|
* viml/parser/expressions: Fix determining invalid commas/colonsZyX2017-10-15
|
* viml/parser/expressions: Fix call inside nested parenthesisZyX2017-10-15
| | | | It may have incorrectly tried to call everything because of essentially “value” nodes being treated as not such.
* viml/parser/expressions: Add a way to represent tokens from C codeZyX2017-10-15
|
* viml/parser/expressions: Add a way to adjust lexerZyX2017-10-08
| | | | | | | It also adds support for kExprLexOr which for some reason was forgotten. It was only made sure that KLEE test compiles in non-KLEE mode, not that something works or that KLEE is able to run tests.
* viml/parser/expressions: Make curly braces name actually workZyX2017-10-08
|
* viml/parser/expressions: Make commas actually work when callingZyX2017-10-08
|
* viml/parser/expressions: Make commas actually work when callingZyX2017-10-08
|
* viml/parser/expressions: Add support for figure braces (three kinds)ZyX2017-10-08
|
* viml/parser/expressions: Start creating expressions parserZyX2017-10-08
| | | | | | | | | | | | | | Currently supported nodes: - Register as it is one of the simplest value nodes (even numbers are not that simple with that dot handling). - Plus, both unary and binary. - Parenthesis, both nesting and calling. Note regarding unit tests: it stores data for AST in highlighting in strings in place of tables because luassert fails to do a good job at representing big tables. Squashing a bunch of data into a single string simply yields more readable result.
* viml/parser: Handle encoding conversionsZyX2017-10-08
|
* viml/expressions: Add lexer with some basic testsZyX2017-10-08
generated by cgit (git 2.34.1) at 2025-04-29 02:03:39 +0000