Closed jeffnye-gh closed 8 months ago
A few general comments (nits):
olympia
are named exactly (case included) as the class they represent. However, this rule isn't documented in the CodingStyleGuide#ifdef
instead of #pragma once
for header guards). Do you mind making them consistent with Olympia's style?{}
Started looking at the implementation. Have some comments pending.
I have posted a PR for the Fusion API alone. We will continue the DSL syntax discussion.
Contains the draft version of the fusion API and start of a test bench. Doxygen file provided also. README.md has the gist. fusion/test/testbench.cpp has some usage.
The API is more general, simpler, better alignment with other source and existing packages (mavis).
See the README.md or front page of doxygen. API uses functor's at the top level and within the inner transform operations for generality. There are examples of each, including a lambda example.
FieldExtractor (mavis) and MachineInfo (future CoreExtensions ?) are template parameters.
To run the test bench and generate docs @ fusion/html/index.html :