Inspecting hundreds of output lines can be quite overwhelming, and the code itself gets cluttered with numerous lines of debugging statements. While print statements can be useful, I have never found them to be very effective. In fact, most Java programmers I know use a combination of a text editor, the JDK, and println statements to develop, debug, and deploy their applications. As a Java programmer, you are probably all too familiar with the () and () methods. So it surprises me that even after all that time, many programmers still primarily use print statements to debug their code.
However, interactive debuggers that allow you to step through your code and inspect your program's variables and view the stack trace have been around since the early 1980s. In addition, print statements can be used for logging and diagnostic purposes. Using print statements is a good way to trace through your code and troubleshoot potential problems. For as long as I have been programming (almost two decades now), I've used some form of a print statement for debugging purposes.
0 kommentar(er)
