undefined | Better HN

0 pointsflohofwoe2y ago0 comments

It's almost impossible to get wrong though, because the same header will also be included in its own implementation. If there's a mismatch between the declaration and implementation you'll get at least compiler warnings.

0 comments

tgv2y ago

It’s been a while, but IIRC there is no problem when you eg. change a struct, as long as the name is the same.

mathstuf2y ago

Indeed. Mismatching headers and libraries is not all that rare. I've seen headers found from Homebrew, libraries from the macOS SDK, and some related tool from `/usr`. Things…rarely work out well, but you only find out in your test suite (or linker if you're really lucky).

flohofwoeOP2y ago

The only realword problem with headers I've seen so far is when there are multiple versions of the same header in the same project (bad idea anyway), and one isn't extremely careful about search paths.

The module equivalent would be different versions of the same module under the same import name. Can the C++ module system actually deal with that?

1 more reply

j / k navigate · click thread line to collapse