in4lio

Yes, I have written a few)) Because this is the most interesting area of programming for me.

Many years ago, I wrote BNF-like language to translate text into syntactic tree, it was part of my graduation project.

I also wrote a Lisp-like lexical preprocessor as an alternative to the standard C preprocessor, it can be used with other languages, for example, with Python.

https://github.com/in4lio/yupp

Fine! To generate the C code using Lisp syntax - it's not such bad idea, the C preprocessor is awful. A few years ago, for this purpose, I wrote the yupp preprocessor which use similar syntax, but yupp allows to inject the code in functional style into the source code on C.

https://github.com/in4lio/yupp/

This is a matter of taste, in this case, IMHO. Thanks for advice)

Oh, yes, I agree. And when I was tired of writing macros like this: https://gist.github.com/in4lio/9102547, I wrote yupp)

Just because C is my primary tool) and I have created yupp, to do things like X Macros simpler.

yupp can even be used with Python, as it allows to make the right indentation, e.g. https://github.com/in4lio/yupp/blob/master/eg/dict.yu-py

Yes, you are right. Since yupp is a third layer, yupp is able to generate C macros, for example:

  ($define,,assert_bit_mask( value, mask, op ),,($do ]
      bool test = ((( value ) & ( mask )) == ( mask ));
      if ( !test ) {
          ut_fault( "expected mask to be set", __FILE__,  __FUNCTION__, __LINE__ );
          op;
      }
  [ ))

will result in:

  #define assert_bit_mask( value, mask, op ) do { \
      bool test = ((( value ) & ( mask )) == ( mask )); \
      if ( !test ) { \
          ut_fault( "expected mask to be set", __FILE__,  __FUNCTION__, __LINE__ ); \
          op; \
      } \
  } while ( 0 )

but you don't need to think about backslashes)