17 Oct
2005
17 Oct
'05
2:03 p.m.
On 10/17/05, Paul Koning <pkoning at equallogic.com> wrote:
That way you reduce the problem to a previously UNsolved problem. Now
you have to solve the futureproofing problem for a more complex
application (the emulator).
paul
Emulators exist for most processors of interest.
QEMU, Bochs, MESS, et al. And they are in C which I think is a good
future-proofing language. At least QEMU and Bochs were designed for
portability. QEMU at present has some weird dependencies on an older verison
of gcc, but I think those are going to go away.
So yeah, pick a portable language and write for portability. But it is quite
likely that system dependecies will occur, so including a system emulator if
one exists is a good idea.
ISTR that whenever the government contracts to have software development
they expect a machine with a complete development environment capable of
building the software purchased. That might be a good idea too.
-- John.