Interfacing to hardware or simulators would, indeed, be cool. Thinking about it brings me to one of my concerns: The Digital Mars compiler.
As best I can tell, it’s a bit dated. In fact, I’ve not yet even found what version of C++ it supports. Also, it doesn’t seem to interface with tools like VS Code to auto-configure, debug, etc. I’ve tried getting VSC & MinGW to generate QSpice component DLLs directly but haven’t found the proper incantation and QSpice errs out loading the DLLs. That ate up a couple of days so, I set it aside for the moment.
Anyway, if there was existing simulator code, DMC might not play nicely with it. Lots of rework might be required. How to solve that has been on my mind.
Absent resolving the DLL linking/loading mysteries, I’ve thought about using the DMC bit minimally and have it connect to non-DMC code client/server fashion – a separate DLL dynamically loaded/linked or some more elegant inter-process communication technique.
Just food for thought.
–robert