Guilt Determination for Abusing the C Preprocessor

[hirrolot]

Date: 04/12/2023

Dear @cospplredman,

This notice is to inform you that, following an extensive investigation, you have been found guilty of abusing the C preprocessor, a serious criminal offense against the principles of code readability and mental stability. The details of the incident leading to this determination are as follows:

1. You wrote the PPLISP_EXP* family of macros in an attempt to dodge Turing-incompleteness of the C preprocessor.
2. You wrote the PPLISP_CONS_ and PPLISP_CONS macros in order to derange the C preprocessor with unbalanced parentheses.
3. You wrote the M_, PPLISP_CALL_, M_PPLISP_CALL, and PPLISP_CALL macros in order to dodge blue painting of the C preprocessor.
4. You wrote the Lisp evaluator using the aforementioned macros, causing the C preprocessor to experience severe pain.
5. You used $ as a non-standard symbol of the function-like macro.
6. Finally, you attempted to hide traces of the crime by the series of #undef directives at the end of the file.

In accordance with our commitment to transparency and community awareness, PPLISP has been added to awesome-c-preprocessor, our public record of similar violations of the law. This record is accessible to the public and serves as a reminder of the importance of code maintainability and engineering sanity.

Sincerely,
The Preprocessor Metaprogramming Police