Declarative, non-intrusive, compile-time C++ reflection for audio plug-ins
Going to ask some really stupid questions, apologies in advance:<p>This is mindblowing work. I&#x27;m having some trouble wrapping my head around all of it. Will lead with the context that:<p><pre><code>  A) I am not very familiar with audio programming specifics, or DSP at all. I have done some things with VST2 + VST3, and looked into LV2.

  B) I have very little background with C++
</code></pre>
I am curious:<p><pre><code>  1. Is this targeted more towards the DSP and algorithm side of audio plugin development, or is there interest&#x2F;use for the plugin side too (IE, generating VST&#x2F;LV2 compatible interfaces)?

  2. Would a byproduct of this be that you would be able to implement functionality + interact with C++ classes from other languages? Or generate C ABI&#x27;s? I see the note: &quot;Automatically generate Python bindings for a C++ class&quot;
</code></pre>
I ask about the second one because I have been trying to work towards getting a C ABI for VST3 so that language bindings can be codegen&#x27;ed. I know VST3 works through COM so you can use that, but the alternative is to emulate the VTable layouts in C structs. This can make it easier than implementing COM in a language.<p>-----<p>Edit: I also wanted to say that when reading your blogpost, the way you write C++ is very easy to understand. Not sure if it&#x27;s a stylistic thing or a purposeful choice. I usually have to spend a second reading C++ code to comprehend it, but in your snippets, I was able to (mostly) grok it first pass.<p>Same for the example code in the repo.