8 ms·
> You can't actually run code from 80's out of the box today (16-bit legacy support has long since stopped being a thing) If you wrote your 1980s C code: 1. U
by einpoklum 7y ago
> You can't actually run code from 80's out of the box today (16-bit legacy support has long since stopped being a thing)
If you wrote your 1980s C code:
1. Using the proper C standard.
2. Using the standard library (and perhaps even common Unix libraries).
3. Were careful not to make assumptions about sizes (which, by the language standard, you shouldn't make anyway).
The your code will compile and work just fine. If you used Makefile's to build it, which you very well may have, and you were using a standard (= Unix) system, there's not a bad chance your build system might work too. :-)
- kllrnohj 7y ago> Using the proper C standard. You mean the standard that didn't exist until 1989? > Using the standard library (and perhaps even common Unix libraries) That's also very late 80s (realistically early 90s) stuff. Which was still yes a very long time ago that C made all these breaking changes, but it was also a good ~20 years after it's release as well.
- einpoklum 7y ago> You mean the standard that didn't exist until 1989? Fair point. But K&R C with System V or BSD libraries will probably-kinda-sorta work.