looking into it a bit, this feels like it should work? at least for basic interop. template support is another matter entirely, but i should be able to expose types and functions from C++ using a wrapper around libclang, and... generate C++ headers to expose my language's interface to C++? maybe? would have to look into how to deal with includes though
@estroBiologist this is wrong and evil feel bad
@barrow TELL ME WHY IT WOULDN'T WORK. FUCKING TELL ME
@estroBiologist JUST!!! AAGH!!!!
@barrow AT *WORST* IT WOULDN'T SUPPORT THE THIRD FORM, WHICH IS A LIMITATION I'M WILLING TO LIVE WITH. THIS IS A VERY EASY, NON-INTRUSIVE WAY OF IMPLEMENTING AUTOMATIC BINDINGS BETWEEN C++ AND COMUNE THAT, IMPORTANTLY, DOESN'T INVOLVE *REIMPLEMENTING THE FUCKING C++ PREPROCESSOR FROM SCRATCH*
@estroBiologist BUT U HAVE TO REIMPLEMENT THE PREPROCESSOR EVERYBODY KNOWS THIS
@barrow SAYS FUCKING WHO!!!!!!!!!
@estroBiologist EVERYBODY!!! IS LIKE, TURING COMPLETE OR SOME SHIT!!!!
@barrow WELL THEM I'M DEFINITELY NOT FUCKING DOING IT!!!!!!!!!!!!!
@estroBiologist FUCK YOU!!!1
could i re-implement (a subset of) the preprocessor to scan source files for includes of comune files, and generate the appropriate headers? is that a reasonable thing to do? probably not but it doesn't SOUND particularly gruelling