X evaluate expression tree in ec_tk_expr
X cmd token
-- example
+X example
X tk_re
cleanup / rework
- better logs
- check return values (-1 or NULL) + use errno
- check missing static / const
-- license: SPDX
+X license: SPDX
- check all completion nodes
X split ecoli_tk.h
- size_t or unsigned int?
X save node path in completion to fix help string
- code coverage
- try to hide structures
-- anything better than weakref?
+X anything better than weakref?
- add ec_node_defaults.[ch] providing usual implementations of node methods
X use vec for strvec
-- ELOOP in case of loop
-- remove weakref?
+/ ELOOP in case of loop
+X remove weakref?
- sh_lex to provide offsets in attributes
- accessors for all structs
====
X register nodes by name
-- interface to add attributes: all nodes must be configurable through a
- generic api
- - attr string
- - attr string list
- - attr node
- - attr node list
- - attr int
-
-- yaml interface to create nodes
+X interface to add attributes: all nodes must be configurable through a
+ generic api:
+ X attr string
+ X attr string list
+ X attr node
+ X attr node list
+ X attr int
+
+X yaml interface to create nodes
- example
examples
- configuration file
- mini shell: cd, ls, cat, stat
- mini network console based on ip
+- dialog-like for use in shell
doc
===
- add make help
- add make config
- -fvisibility=
+- use meson
tests
=====
=========
- regexp
-- node which always matches
-- file + partial completion
+X node which always matches
+X file + partial completion
- ether, ip, network
-- fusion node: need to match several children, same for completion
+- fusion node: need to match several children, same for completion?
- float
- not
+- reparse: parse a tree with received strvec, then another tree
+ with strvec generated from first tree
encoding
========
netconf example
===============
-- demonstration example that parses yang file and generate cli
+/ demonstration example that parses yang file and generate cli
---------------
+about split in several libraries
+
+There are several options:
+
+1/ one library, config options to select libyaml, libedit
+ - need to manage dependencies in build system
+
+2/ one library for ecoli-core, one for ecoli-yaml, one for
+ ecoli-edit
+ - extra complexity
+
+3/ one library with core + yaml + edit
+ dependency is managed at runtime
+