3 ms·

Or why not any compiler from the last 15 years

• FartyMcFarter 4y ago
  If it ain't broken, don't fix it. What's the point of updating an old game's source tree to compile with the latest and greatest compilers? Even if one wanted to do that, it would probably be best done as a fork.
  • unixhero 4y ago
    Well because GCC
• mysterydip 4y ago
  Sometimes the code was written specifically for nuances of a given compiler, and compiling the same code on a different one would produce side effects.
  • bluedino 4y ago
    For one, the inline assembly syntax wasn't exactly the same. When I was a kid I had a DOS game programming book, the worst thing about it was that it came with the Microsoft C compiler. EVERYONE used Borland back then. So most of the sample code and shit you would find on the AOL forums or BBS's wouldn't work. Sure, if you knew assembly and your compiler it was probably trivial to get it working. Same goes for functions to call interrupts and things like that.
• petercooper 4y ago
  If you had two compilers for the same language from different companies back in the 80s or 90s, the chances of them both successfully compiling the same codebase without any changes was slim to none. A bit like sharing SQL between Postgres, SQLite, SQL Server and Oracle nowadays.