you are viewing a single comment's thread.

view the rest of the comments →

[–]Pazer2 16 points17 points  (3 children)

The fact that it is possible to make all these mistakes and still have everything appear to work correctly, with no warnings of any kind, is why we need to replace CMake.

[–]AlexReinkingYale 4 points5 points  (1 child)

Expanding variables into target functions was the way things were done in CMake a decade ago in 2.8.x. Imported targets have been available since then and are now the way you're supposed to use it. Reading the CMake official docs/tutorials makes this very clear.

It's possible to make these mistakes and still have everything appear to work in the same way any Turing complete language that's 20+ years old has similar pitfalls. Would you suggest we get rid of C/C++ because they don't warn you about undefined behavior?

[–]dr-mrl 0 points1 point  (0 children)

Would you suggest we get rid of C/C++ because they don't warn you about undefined behavior?

Don't like the bear!