I'd like to eventually remove GCC as a dependency for building the project to make this more portable, and instead only require python for development and testing + glmatrix for matrix maths.
I'm not super sold on keeping the cpp macro syntax either. This will probably be something to read in special javascript, apply some transforms, and output valid javascript. Not unlike how the glsl->glsl compiler works.
The most quixotic thing I want from this is to allow for a lispy syntax, specifically to clean up the code generation stuff introduced in #232.
My main requirements:
allow for existing macros to work
option to "break out into lisp"
syntax highlighting works unchanged in both emacs and github
code generation features (see lispy bits)
This isn't needed right away, but would be nice to have in the future.
mldulaney
commented
8 years ago
I'd like to eventually remove GCC as a dependency for building the project to make this more portable, and instead only require python for development and testing + glmatrix for matrix maths.
I'm not super sold on keeping the cpp macro syntax either. This will probably be something to read in special javascript, apply some transforms, and output valid javascript. Not unlike how the glsl->glsl compiler works.
The most quixotic thing I want from this is to allow for a lispy syntax, specifically to clean up the code generation stuff introduced in #232.
My main requirements:
This isn't needed right away, but would be nice to have in the future.