Vandalix Code
Brought to you by:
v-andal
File | Date | Author | Commit |
---|---|---|---|
src | 2016-11-21 |
![]() |
[b68a08] Slight fixes in documentation |
test | 2016-04-28 |
![]() |
[1fb373] Added detached execution |
.gitignore | 2014-03-21 |
![]() |
[846c16] Functions and lot's of other stuff |
README | 2016-04-28 |
![]() |
[1fb373] Added detached execution |
make_maker.pl | 2014-12-29 |
![]() |
[1157ac] Added RPC server that uses Vandalix |
This directory contains sources for Vandalix framework. There are also few modules and program examples that use them. Directory "src" contains the code of the framework itself. Directory "test" contains example interpreter and example of Vandalix code. In that directory run "make" (or "gmake") to compile everything. Run "./vx_run" without any arguments to get syntax of supported Vandalix code. It is printed to stdout. You can try to execute some of Vandalix scripts by calling for example "./vx_run aliases.vx". See "test/README" for more details. See src/vandalix/vx.h for the API of Vandalix parser. The file also contains documentation in POD format, which can be viewed using command perldoc src/vandalix/vx.h Directory src/vxm_base contains implementation for most of the parsers used in vx_run.c Directory src/vxm_secu contains stuff used for signatures processing. Directory src/utils contains some commonly used utilities as well as header vx_api.h defining interface for calling Vandalix opcodes. Directory src/db contains files used to access SQLite DB with users info. Directory src/evtid contains framework for working with network sockets and timers Directory src/evdlstn contains small library for listener that works with evtid library Directory src/ui_ctrl contains Vandalix modules necessary to work with network socket The Vandalix framework is created not as general-purpose programming language. It shall be used for creating set of procedures that can be used for configuring some running system. In general, the interpreter shall receive (possibly signed) code over network and then execute it sending back whatever output this code has produced.