>Mark used TurboC; I don't know how much of this applies to MSC.
What version of Turbo C? Does it make a difference? Is it in fact Turbo C
rather than the much bigger Borland C/C++?
The reason I'm asking is, I want to buy a compiler to do my own MS-DOS
building. In particular, I have this fantasy: Python, built for an HP-95LX's
System Manager, in the multi-taskable .EXM format, to execute out of the
ramdisk image. This would cut the memory requirements in half, and allow
hot-keying between python and (e.g.) Freja. If I get that much done, then
I'd like to dabble with trying to teach the MS-DOS Python to handle packages
in overlays the way the Unix Python does foomodule.o.
Then if I could just get a custom prom burnt, with Python and all its
packages in place of Lotus 123....