On Tue Aug 12 17:10:20 2025 +0000, Rémi Bernon wrote:
The MR now generates code that is #included, but there still is a macro, which we are arguing about, which lists all the functions which are expected to be implemented, in a "class vtable", so you can't miss one when using it. There might be other ways than a macro, but its purpose is however that it allows compilation errors over link errors and I think it's an important criteria not to be discarded.
What I'm saying is that we can use Jacek's proposal above, but instead of putting it in a .c file, it's put in .h included from the implementation, and then myint_dec() et al. are static. That would cause compiler errors rather than linker errors, as you desire, and would be better for the compiler anyway as they can be inlined. Am I missing something?