Re:Banned C standard library functions in Git source code
by ShinTakuya on Sunday August 25, 2019 @08:37PM
(#20796660)
Regarding remaining compatible, I would argue that this is why modern languages implement lock files and version pinning. If you don't like a particular change but need some extra functionality or a security fix you can fork the relevant libraries or extend the functionality with an extra self written library.
Re:Banned C standard library functions in Git source code
by riquito on Sunday August 25, 2019 @08:51PM
(#20796713)
It's not a guarantee that it will work, it's not that rare to encounter a minor/patch version in a library that introduced some subtle incompatible change (usually unbeknownst to the author)
Re:Banned C standard library functions in Git source code
by ShinTakuya on Sunday August 25, 2019 @09:53PM
(#20796914)
That's literally the purpose of the lock file. The lock file locks the entire dependency tree. So unless you're bumping versions or you fail to save the lock file, the entire dependency tree's versions will remain the same.
>some subtle incompatible change
In statically typed languages this normally isn't an issue. Of course I'm aware that logic can also be changed, but in that case it's up to you to write appropriate tests (or just don't bump the versions of your libraries without a good reason).
Re:Banned C standard library functions in Git source code
by Volt on Monday August 26, 2019 @12:21AM
(#20797445)
It still sucks. I have a few Haskell projects from a few years ago that I wanted to compile on another system. So I froze the dependencies, moved the project, and tried to build. Solver failed. I gave up.
Re:Banned C standard library functions in Git source code
by ShinTakuya on Monday August 26, 2019 @12:30AM
(#20797472)
As far as I'm aware, Haskell's dependency system doesn't have a lock file. That's the key part to keeping things stable. Version pinning alone isn't enough.
Re:Banned C standard library functions in Git source code
by rubber_duck on Sunday August 25, 2019 @06:58PM
(#20796199)
You had the unfair advantage of working on your own :)
Re:Banned C standard library functions in Git source code
by adamnemecek on Sunday August 25, 2019 @05:22PM
(#20795687)
This is a C++ dependency manager problem though.
However, here's the upshot-- that awful, buggy, custom solution is guaranteed to remain compatible with the codebase that contains it. You won't find a single instance where such a dev "improved", "refactored", "optimized", or "modernized" that awful, buggy code in a way that stopped the rest of the code from working and then shipped that broken blob of junk. And if you did find that, there's no way they'd convince the rest of the devs that this is a useful thing to do in the interest of "moving forward" or whatever.
On the other hand you'll find zillions of dollars spent on systems to keep dependency management tools from causing exactly that problem.
Just to give a real-world example-- a user reported that an abandoned C++ plugin wasn't working. We did a race:
1. Three devs try to get a single C++ dependency of that plugin to work cross platform (OSX, Windows, Linux).
2. I tried to port the C++ plugin to a C plugin with no deps.
By the time I ported, tested, and shipped, those three devs were tracking down a bug with the build script of the C++ dependency on Windows.
Edit: granted the plugin itself is only about 2000 lines of code.