Define the format for a .config
file (file suffix name subject to change)
- Define the lexing rules format
- How will the user specify how to tokenize the instruction file?
- The user should be allowed to provide a regular expression to match or manually encode the Finite State Machine that matches tokens.
- Define the parsing rules format
Useful links:
Extensions:
- Is it possible to make a "un-parser" that converts an AST into another language? Perhaps, if this is possible, it might be possible to transpile any language supported by the APLI to another language that is supported by the APLI.
clang -D DEBUG -D COLOR -D MEMORY_CHECK -fsanitize=address -fno-omit-frame-pointer -O2 test/lexer/lex_test.c ; ./a.out; rm a.out;
To create a bash profile:
LD_PRELOAD=/usr/local/lib/libprofiler.so CPUPROFILE=test.prof ./a.out test/integration/resources/complex/very_long_lisp_program.lisp