Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • 4
    This all sounds horrible... Commented Sep 28, 2016 at 10:28
  • 1
    Please, John, don't do this anywhere in production. Learn a better way. Commented Sep 28, 2016 at 11:37
  • Usually msglevel=0, so nothing's displayed. Also, there's typically a corresponding fprintf at the entry point of each function, displaying all inout arguments, to the extent feasible. That way, when there's a bug, you bump msglevel, and immediately see the entire program flow, along with all function inputs/outputs. Usually (though not 100% always) way better than running the debugger and setting breakpoints. And most languages don't have multiple entry points for functions (Fortran being an exception). Multiple return points are typically a similarly less-than-ideal idea. Commented Sep 29, 2016 at 7:18
  • Every time I feel tempted to add such “headings comments” indicating what the following block of code does next, I know that I should refactor. Commented Sep 29, 2016 at 17:49