java 中我們很常見的設計 API 的例子是對一個對象進行增, 刪, 查,改.

比如

Object addObject(Object obj);

Object delObject(Object obj);

Object modifyObject(Object obj);

成功返回 obj, 不成功(參數不合法,或已經存在, 或不存在)拋出異常

還是

int addObject(Object obj);

int delObject(Object obj);

int modifyObject(Object obj);

如果成功返回 0, 不成功, 返回其他數字

還是

boolean addObject(Object obj);

boolean delObject(Object obj);

boolean modifyObject(Object obj);

如果成功返回 0, 不成功(參數不合法,或已經存在, 或不存在), 拋出異常

感謝各位熱心回答, 我已經決定采用第一種方式了.原因: 1. 性能不是那么的關鍵; 2

絕大多數我們認為參數是正確的.排除異常較返回 Errorcode 讓代碼更加簡潔.

補充: 以下是從 這里 找到的一個回答, 基本決定采用第一中方式, 這或許是 java 語言本

身的特點, 如果是 c 或 cpp 我更傾向于第二種方式.

Exceptions impose quite an overhead on the runtime performance, but makes reasoning about the program flow drastically easier. This reduces faulty programming (semantic errors), especially as it forces you to deal with them - they 'fail securely' by terminating the program if they are ignored. They are ideal for 'situations which are not supposed to happen'. Also they can transport metadata like a stacktrace.

Error codes, on the other hand, are light-weight, fast, but forces the method caller to explicitely check them. Failure to do so often results in program flaws, which can range from silent data corruption, security holes, to nice fireworks if your program happens to be running inside a space rocket.

總結

以上是生活随笔為你收集整理的java 设计方法_java 中如何处理设计一个方法的全部內容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網站內容還不錯，歡迎將生活随笔推薦給好友。