> c2nim does that, yes. No idea why you are all so keen on using a C > preprocessor to throw away lots of useful information.
@Araq haha spoken like a compiler developer: every token is precious! ;) More seriously the C Macros tend to just add crap on top of the C code like fake-namespacing or C compiler compatibility that's not needed in Nim. As a general note almost every C macro I've manually converted was done better with proper Nim features after expanding the raw C macros. They're just not worth it, except in a few cases where you need to manually write them anyway to get the types. To the point @Pmunch makes it's more about just getting to use the C project. I prefer spending time making a nice Nim api on top of the raw C one than trying to tweak the C bindings themselves to be nicer. > dynlib is definitely something I should do a writeup on at some point, but I > think I want to get this fixed first: > <https://github.com/nim-lang/Nim/issues/21403> Oh, I didn't think of that sort of thing. Mostly I use one-time load dynlibs.
