Why “not all control paths return a value” is warning and not an error?

by

Failing to return a value from a function that has a non-void return type results in undefined behaviour, but is not a semantic error.

The reason for this, as far as I can determine, is largely historical.

C originally didn’t have void and implicit int meant that most functions returned an int unless explicitly declared to return something else even if there was no intention to use the return value.

This means that a lot of functions returned an int but without explicitly setting a return value, but that was OK becase the callers would never use the return value for these functions.

Some functions did return a value, but used the implicit int because int was a suitable return type.

This means that pre-void code had lots of functions which nominally returned int but which could be declared to return void and lots of other functions that should return an int with no clear way to tell the difference. Enforcing return on all code paths of all non-void functions at any stage would break legacy code.

There is also the argument that some code paths in a function may be unreachable but this may not be easy to determine from a simple static analysis so why enforce an unnecessary return?

More Related Contents:

  1. Why should I always enable compiler warnings?
  2. Multi-character constant warnings
  3. Selectively disable GCC warnings for only part of a translation unit
  4. What does casting to `void` really do? [duplicate]
  5. How to turn on (literally) ALL of GCC’s warnings?
  6. Does there exist a static_warning?
  7. Why does C++ code missing a formal argument name in a function definition compile without warnings?
  8. What’s up with the thousands of warnings in standard headers in MSVC -Wall?
  9. Override compile flags for single files
  10. Is using #pragma warning push/pop the right way to temporarily alter warning level?
  11. How do you disable the unused variable warnings coming out of gcc in 3rd party code I do not wish to edit?
  12. What’s the point of g++ -Wreorder?
  13. Will a “variableName;” C++ statement be a no-op at all times?
  14. g++ How to get warning on ignoring function return value
  15. How can I turn on (literally) ALL of GCC’s warnings?
  16. C++ Boost: what’s the cause of this warning?
  17. Is it wise to ignore gcc/clang’s “-Wmissing-braces” warning?
  18. Why should I initialize member variables in the order they’re declared in?
  19. Understanding -Weffc++
  20. Can I make GCC warn on passing too-wide types to functions?
  21. how to control one program from other
  22. Is short-circuiting logical operators mandated? And evaluation order?
  23. How can I create directory tree in C++/Linux?
  24. understanding of pthread_cond_wait() and pthread_cond_signal()
  25. Configuring compilers on Mac M1 (Big Sur, Monterey) for Rcpp and other tools
  26. How to solve ——-undefined reference to `__chkstk_ms’——-on mingw
  27. details of std::make_index_sequence and std::index_sequence
  28. Why doesn’t emplace_back() use uniform initialization?
  29. Virtual dispatch implementation details
  30. How to benchmark Boost Spirit Parser?

Leave a Comment