4 X evaluate expression tree in ec_tk_expr
12 - ec_completed_item_update()
13 - ec_completed_item_set_display_value()
18 - properly manage quotes in shlex
19 X remove the _new() functions
20 - iterate children nodes without chaining them
21 - add a tk vector type: will be used in several nodes (ex: or, seq, ...)
22 - check allocation model everywhere
24 - use linux style (update .emacs)
27 - use errno when returning pointers
28 - missing static / const
29 - license: "s/neither the name...may/the names of its contributors may not/"
30 - check all completion nodes
32 - cache results when appropriate?
33 - size_t or unsigned int?
36 X ec_parsed_tk -> ec_parsed
37 X ec_completed_tk -> ec_completed
38 X tk, gen_tk, token, ... -> node
39 X tokens -> input_str / input_strvec ?
40 - use is_err() or errno for funcs returning ptrs, or use errno for all funcs
41 - save node path in completion to fix help string
43 - try to hide structures
44 - anything better than weakref?
45 - add get_max_parse_len() for all relevant nodes
46 - add ec_node_defaults.[ch] providing usual implementations of node methods
52 X pass the current parsed state when parsing/completing
54 - new node "condition"
64 X register nodes by name
65 - interface to add attributes: all nodes must be configurable through a
73 - yaml interface to create nodes
79 - example which parses arguments (argc/argv)
80 - example that acts as bash completion (ip link ?)
81 - calculator example (var assignation, expression evaluation)
82 - example with libedit
83 - mini script language
91 - generate automatic api doc
93 - coding rules, process
96 - say that it stops at first match (no ambigous support)
97 - say that completion must be exhaustive
103 - split libs, tests and examples
111 - complete automatic tests with "make test"
117 - node which always matches
118 - file + partial completion
120 - fusion node: need to match several children, same for completion
127 - support utf-8 and other encodings
134 - demonstration example that parses yang file and generate cli
138 -----------------------
142 [tab] list possible completions (matches only)
143 [?] list what is expected, example:
145 "command [foo] toto|titi|<int>"