0b2240e6e4
Summary: Split up `process-file` so that looking at the generated code for an LCP form is easier from the REPL. `process-lcp`, `generate-hpp` and `generate-cpp` now perform the generation of C++ code, but take a list of "C++ elements" (the results of LCP forms) as input and write their output to streams. They do no reading/evaluating of LCP forms of their own. `read-lcp` and `read-lcp-file` are used to read and evaluate a stream of LCP forms. The latter is a specialized version for file streams which also reports the position of the form within the file when an error happens. `process-lcp-string` and `process-lcp-file` are convenient wrappers around the main functionality that take a string (file) and output to strings (files). Using `read-lcp` and `read-lcp-file` they process LCP forms and pass them off to `process-lcp` for code generation. Reviewers: mtomic, teon.banek Reviewed By: teon.banek Subscribers: pullbot Differential Revision: https://phabricator.memgraph.io/D2097 |
||
---|---|---|
.. | ||
apollo | ||
emacs-lcp | ||
gdb-plugins | ||
plot | ||
src | ||
tests | ||
vim-lcp | ||
.gitignore | ||
analyze_rpc_calls | ||
arc-clang-tidy | ||
CMakeLists.txt | ||
coverage_binary | ||
lcp | ||
manage_distributed_card_fraud | ||
memory_usage | ||
mg_import_csv.dockerfile | ||
neo_to_memgraph | ||
requirements.txt | ||
setup | ||
snapshot_recovery_speed |