[Simh] SIMH as a library

Seth Morabito web at loomcom.com
Mon Oct 16 18:53:09 EDT 2017


Hello all,

Has any thought ever been put into whether or not it might be a good
idea to decouple the emulator implementations (VAX, PDP, CDC, SAGE, and
so on) from the core SCP functionality?

I ask because I've been working on my SIMH-based 3B2 emulator again
after quite a few months away. Because I let it sit so long, I threw
away my old SIMH working directory and built a new one from the latest
SIMH source code, dropping my "3B2" directory into it and making the
necessary changes to the makefile.

It's always been my intention to submit the 3B2 emulator to the core
SIMH package once it was in a usable state, but that means Mark is
saddled with maintaining the 3B2 source code and dealing with pull
requests for it. I think it would be nice if Mark could focus on the SCP
functionality, and let individual emulator developers use it as a
library. It could be built as libscp.a, libscp.so, libscp.dylib, or
LIBSCP.DLL (depending on the platform) and just pulled in as a
dependency for the individual emulators, each of which could then live
in its own source code repository. (Of course, the downside to this is
that the emulators wouldn't instantly get SCP bugfixes, which is very
nice)

I haven't given this a LOT of thought, and I'm more or less thinking out
loud here, but I would love feedback. Good idea? Bad idea?

-Seth
-- 
  Seth Morabito
  web at loomcom.com


More information about the Simh mailing list