java软件开发中可能出现几个错误观点（Several misconceptions may arise in Java Software Development）.docVIP

java软件开发中可能出现几个错误观点（Several misconceptions may arise in Java Software Development） Do you think you are a Java expert? Sure they have complete control of the Java exception handling mechanism? In this code, you can quickly identify six problems of exception handling? OutputStreamWriter = out... Java.sql.Connection = conn... Try {/ / an Statement = conn.createStatement (STAT); ResultSet (rs = stat.executeQuery Select uid, name from user\); While ((rs.next)) { Out.println (ID:\ + rs.getString (uid\) / /. , the name: + rs.getString (name\)); } (conn.close); / / 3 (out.close); } Catch (Exception Ex) / / 2 { (ex.printStackTrace); / / 1, 4 } As a Java programmer, you should at least be able to find two questions. However, if you cant find all six questions, please continue reading this article. The general principle is discussed in this paper is not a Java exception handling, because these principles have been known to most people. We want to do is to analyze all can be called counterexamples (anti-pattern) against the common bad habits good encoding standard. To help readers familiar with the typical example, which can perceive and avoid these problems in practical work. One of the counterexamples: discard abnormal Code: 15 -18 line. This code capture abnormal but not any treatment, can be regarded as the killer in Java programming. The point of view from the frequent problems and harm degree, as a notorious it may and C/C++ program the problem?? Do not check whether the buffer is full. If you see this discarded (not thrown) abnormal situation, be sure to code ninety-nine percent problems (in rare cases, this code has the reason of existence, but the best and complete notes, so as to avoid the misunderstanding of others). This code is wrong, abnormal (almost) always means something wrong, or at least have some unusual things, we should not be on the program issued a distress signal to keep silent and completely indifferent. What is called printStackTrace not exception ha