Unreachable code: error or warning? [closed]

by

An error means that the compiler is physically unable to deal with your code.

A warning means that the compiler is capable of dealing with your code, but it believe that what you have written is wrong in some way.

It seems pretty clear cut to me – it should be a warning.

Besides, what about the case where I’ve decided to shorten a method for debugging purposes:

public bool ShowMenu()
{
    return true;
    /* The standard implementation goes here */
}

I know its wrong, but for the compiler to ask me to also comment out that code would just be a pain.

More Related Contents:

  1. Learning to write a compiler [closed]
  2. What is an application binary interface (ABI)?
  3. Writing a compiler in its own language
  4. Bootstrapping still requires outside support
  5. Conventions for exceptions or error codes [closed]
  6. How does an interpreter/compiler work
  7. How was the first compiler written?
  8. Why don’t languages raise errors on integer overflow by default?
  9. Zero-based month numbering [closed]
  10. Learning Resources on Parsers, Interpreters, and Compilers [closed]
  11. Correct suffix for Fortran 2003 source file – Intel Fortran compiler
  12. Why are const parameters not allowed in C#?
  13. History of trailing comma in programming language grammars
  14. What’s the difference between parse trees and abstract syntax trees (ASTs)?
  15. Why are compilers so stupid?
  16. Compiling a Java Class in memory with `lombok` annotations and Java JDK 8
  17. ios5 ARC what is the compiler flag to exclude a file from ARC?
  18. How does compiling circular dependencies work?
  19. Suggestions for writing a programming language? [closed]
  20. How does the Go1 compiler work?
  21. How do I compile and run a C program in Sublime Text 2?
  22. Are Fortran control characters (carriage control) still implemented in compilers?
  23. Maximum Method Name Length
  24. Bootstrapping a compiler: why?
  25. What is tail recursion?
  26. Algorithm for finding the fewest rectangles to cover a set of rectangles without overlapping
  27. When should I mock?
  28. Why isn’t Array a generic type?
  29. Does concatenating strings in Java always lead to new strings being created in memory?
  30. error: writable atomic property cannot pair a synthesized setter/getter with a user defined setter/getter

Leave a Comment