4 ms·
> I couldn't disagree more. It's a cute trick but not useful that code from 80's is still compilable with a compiler from 40 years later. Still a good number o
by adev_ 7y ago
> I couldn't disagree more. It's a cute trick but not useful that code from 80's is still compilable with a compiler from 40 years later.
Still a good number of packages you are using right now on your Linux distribution have a core more than 15-20 years old and still they compile only with minor modifications with the last GCC.
Compatibility does matter. It should however not prevent evolution. If handle properly, nothing block us to get a proper versioning and evolution path on the toolchain we use.
And on many aspect C++ up to now has been very successful to do that.
> You can't actually run code from 80's out of the box today
Good C is close to immortal. Doom is from 93, and still you can compile it and run it with the last compiler in 2020 with minor modifications.
- kllrnohj 7y agoOf course compatibility matters but as you noted (twice!) it's not perfect and doesn't need to be. Minor modifications are necessary to keep up. That's all that's being proposed by the paper. So now we're just debating the size of ongoing breakages instead of just their existence. And no good C is not close to immortal. Good luck compiling K&R C with modern compilers, for example.