blocks|key|61055|text|明确地为所有不同的情况定义新的异常。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|61056|假设你正在实现一个解释器/编译器。你会有像SemanticVerifier，解释器，CodeGenerator+(当然还有其他)这样的模块。你想知道当你的程序崩溃时会抛出什么样的异常。哦，这就是语义！看，翻译器里有个bug！您希望用户知道，这样他就可以报告更精确的错误。|61057|我个人认为，如果每个模块都有单独的异常，那么它会带来更好的设计。|61058|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Definitely defining new exception for all different cases. 

Imagine you are implementing an interpreter/compiler. You gonna have modules as SemanticVerifier, Interpreter, CodeGenerator (and others of course). You want to know what kind of exception gonna be thrown when your program crash. Oh there it's Semantic! there look it's a bug in the Interpreter! And you want the user to know so he can report a more precise bug.

I personally think it leads to a better design if you have separate exceptions for every module.

blocks|key|60584|text|为用户关心的每种错误定义一个新的异常。因此，例如，理想情况下，您应该在程序中捕获NullPointerException，并将其转换为程序的用户级可以报告“软件错误检索客户”的CustomerLookupException。Exception+chaining在这方面很方便，因为您也可以传递原始异常。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|60585|整个Java+Tutorial+on+exceptions是一个很好的资源。|60586|entityMap|0|LINK|mutability|MUTABLE|url|http://docs.oracle.com/javase/tutorial/essential/exceptions/chained.html|1|http://docs.oracle.com/javase/tutorial/essential/exceptions/index.html^0|34|I|0|0|2|R|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

Define a new exception for each kind of error that matters to your user. So, for example, ideally you should catch NullPointerException inside your program, and turn it into a CustomerLookupException to that the user level of the program can report "Software error retrieving customer." <a href="http://docs.oracle.com/javase/tutorial/essential/exceptions/chained.html" rel="nofollow">Exception chaining</a> is handy for this, as you can pass along the original exception as well.

The whole <a href="http://docs.oracle.com/javase/tutorial/essential/exceptions/index.html" rel="nofollow">Java Tutorial on exceptions</a> is a good resource.

blocks|key|61112|text|您应该为每种情况定义一个新的异常。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|61113|原因是这样每个Exception都可以独立处理。|offset|length|style|CODE|61114|例如，以不同的方式捕获Exception允许您在某些情况下继续，或者在其他情况下结束。|61115|entityMap^0|0|7|9|0|B|9|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@$D|Q|E|R|F|G]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|K|$]]

You should define a new exception for each case.

The reason is so that each <code>Exception</code> can be handled independently.

For example, catching the <code>Exception</code>s differently allows you to either continue in some cases, or end in others.

blocks|key|5312796|text|在我看来，你的第一个选择更合适|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5312797|(1)为整个应用程序定义一个单独的异常，该异常接受字符串msg并显示它。并且在具有适当的地点特定消息的所有地点使用它。|5312798|即使我在应用程序中使用了单个异常。如果为每种类型创建单独的异常，则会增加复杂性。它会有很多冗余的代码。为了表示不同类型的异常，您可以在通用异常本身中传递一个参数(类型或其他)。|5312799|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

in my view your 1st option is more suitable

(1) Defining a single exception for whole application which takes a string msg and displays it. And using it at all places with appropriate place specific message.

Even i am using a single exception in the application. If you create separate exception for each type it will increase complexity. It will have lot of redundant code.
For denoting different type of exception, you can pass a parameter(type or something) in the common exception itself.

Which is a better approach to exception handling and why?:

(1) Defining a single exception for the whole application which takes a string message and displays it. Use this exception everywhere with a specific message appropriate to the scenario.

I have no idea why this is not appropriate.

(2) Defining a new exception class for each different case in the application.

I feel this is not appropriate because there are cases where the exception is at just one place in the application. e.g. amount entered is -ve Is it ok to create a whole new exception class just for a single case in the app ?

Which way is better for exception handling

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

哪种异常处理方法更好?为什么？：(1)为整个应用程序定义一个单独的异常，该异常获取一个字符串消息并显示它。在任何地方都使用此异常，并使用适合于该场景的特定消息。我不知道为什么这是不合适的。(2)为应用程序中的每个不同情况定义一个新的异常类。我觉得这是不合适的，因为在某些情况下，异常只出现在应用程序的一个位置。例如，am...

问哪种方法更适合处理异常
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问哪种方法更适合处理异常EN