> Not sure how relevant this is for C++, but soon we will be sending a > proposal to Automake for supporting non-optional dependencies and thus > having native support for Algol 68, Fortran and Go modules/packages.
Highly relevant. Actually it would also concern Ada, Haskell, etc. because all “compiles into an intermediate binary representation” module systems are alike. It’s just that people expect more from C++ and C++ indeed has a far more complex context. For example, Fortran modules’ intermediate representation also has the incompatibility problem, but far as I know Fortran users just manually manage them. A Fortran user told me he just makes a directory to place the intermediate files for every set of compilation flags he needs. Whereas in C++, people expect package managers/build systems to automatically solve this problem. This could be interesting! I’m not familiar with Automake’s evolution process. Where would you be sending the proposal, Automake mailing list?
