blocks|key|175919|text|正如其他人指出的，一般规则是:不要捕获无法处理的异常。考虑到您知道该做什么，您应该单独捕获这8个异常，参见准则1。您不应该捕获Exception的原因是，您也会捕获诸如ThreadAbortException这样的关键异常，这是您根本不应该做的。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|175920|1：http://msdn.microsoft.com/en-us/library/ms229005.aspx。|175921|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/ms229005.aspx^0|1R|9|2C|K|0|2|1H|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]|$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|U|8|@]|D|@$9|V|A|W|1|X]]|E|$]]|$1|H|3|-4|5|6|7|Y|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]]]

As others have pointed out the general rule is: Do not catch exceptions that you cannot handle. Given that you know what to do, you should catch the 8 exceptions individually, see guidelines [1]. The reason why you should never catch <code>Exception</code> is that then you would also catch critical exceptions like <code>ThreadAbortException</code>, which you really never should do.

[1]: <a href="http://msdn.microsoft.com/en-us/library/ms229005.aspx" rel="nofollow">http://msdn.microsoft.com/en-us/library/ms229005.aspx</a> .

blocks|key|195951|text|正确的操作是忽略它们，除非您能够真正修复它们。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|195952|它们将传播到调用代码，这些代码可能能够修复它们，或者记录它们，或者其他什么。但是，除非你能在你的水平上改善这种情况，否则就不要抓住它们。|195953|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

The correct action is to ignore them, unless you can actually fix them.

They will propagate to calling code which might be able to fix them, or log them, or something. But unless you can improve the situation at your level, don't catch them at all.

blocks|key|2315635|text|如果你知道如何处理它们(例如，如果你能补救这种情况)，或者在你的水平上处理它们是有意义的，那么就抓住它们。否则，让高级代码来处理它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2315636|还有一件事。如果要让高级代码处理异常，还可以捕获异常并将其“包装”，然后使用不同的异常对象，然后抛出异常。新的例外应该是在高级代码(即调用使用API的代码的代码)上下文中有意义的异常。通常，这是一种很好的方法，可以阻止有关低级代码的细节“泄漏”到更高级别(实质上是停止抽象泄漏)。|2315637|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Catch them if you know what to do with them (i.e., if you can remedy the situation), or if it makes sense to handle them at your level. Otherwise, let higher-level code handle it. 

Another thing. If you are going to let higher-level code handle the exception, you can also catch the exceptions and "wrap" then with a different exception object, and then throw that. The new exception should be one that makes sense in the context of the higher-level code (i.e., the code that is calling your code that uses the API). In general, this is a good method to stop details about lower-level code from "leaking" into higher levels (essentially you're stopping abstraction leakage).

blocks|key|175852|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|175853|用于使用异常(如参数异常或空引用)，在它们发生之前，通过强制断言防止它们发生，并在调用链上进行检查，以便尽早识别违规输入。例如，您应该要求用户键入的路径在传递到任何进一步调用之前进行验证。如果确实引发使用异常，则不应捕获它们(除非您的最后一个记录器和您无法控制的礼貌的executioner.)|unordered-list-item|175854|For异常(例如一个文件在初始检查之后消失)，如果可以或需要调用方法来进行检查和处理，则在调用点处理它。这都取决于如果无法再找到文件，您的系统应该做什么，例如.|175855|。|175856|entityMap^0|0|0|0|0^^$0|@$1|2|3|-4|4|5|6|J|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|K|7|@]|8|@]|9|$]]|$1|D|3|E|4|C|6|L|7|@]|8|@]|9|$]]|$1|F|3|G|4|5|6|M|7|@]|8|@]|9|$]]|$1|H|3|-4|4|5|6|N|7|@]|8|@]|9|$]]]|I|$]]

<ul>
<li>For usage exceptions (like argument exceptions or null references), prevent them before they occur by enforcing assertions and checks all the way up along your call chain so that the offending input is identified as early as possible. For instance, you should require that a path typed by a user is validated before it ever gets passed into any further call. If usage exceptions do get thrown, they should not be caught (except by your final logger and polite executioner.)</li>
<li>For exceptions beyond your control (such as a file disappearing after you initially checked for it), handle it at the calling point if you can or require a calling method to make the check and handle it. This all depends on what it makes sense for your system to do if the file can no longer be found, for instance.</li>
</ul>

blocks|key|2315678|text|另一种思考这个问题的方法是捕捉所有异常，如果上面的层不知道如何处理异常，那么上面的层就会接收异常。我将终端用户作为一个“层”，以及其他不例外的系统。因此，最终用户，作为人类(!)无法处理本机格式的异常，因此可以捕获代码中的所有异常并将其转换为友好的人工格式，例如屏幕上的错误消息。例如，在Windows窗体中单击事件处理程序按钮。类似地，如果调用代码的系统不知道异常，则需要将异常编组成其他系统可以处理的格式。这也是记录异常的地方。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2315679|否则，您只需要在可以执行某种恢复的情况下捕获异常，或者希望添加更多信息(包括原始异常作为innerException)，这两者都往往是异常，而不是常规。|2315680|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Another way to think about this to catch all exceptions where the layer above that would otherwise receive the exception does not know how to handle exceptions. I include the end-user as a "layer", and other systems that are not exception aware. So the end-user, being human (!) cannot handle an exception in its native format, so you could catch all exceptions in your code and convert them into a human friendly format, e.g., a error message on the screen. This handling code would be, e.g., in the button click event handler in a Windows form. Similarly, if the system calling your code is not exception aware, then you need to marshal the exception into a format the other system can handle. This is also the point where you would log the exception.

Otherwise, you only need to catch an exception if you can perform some kind of recovery, or you want to add further information (include the original exception as the innerException), both of which tend to be the exception not the norm.

I have the following lines of code:

<pre><code>FileInfo dbFile = new FileInfo(fileName);
dbFileSize = (long)dbFile.Length / 1024;//KB
</code></pre>

There are 8 possible exceptions from <code>new FileInfo(fileName)</code> and <code>dbFile.Length</code> calls. I cannot just ignore them. I have to catch them.

What you are going to do with those 8 exceptions? Catch them separately (too many lines)? Catch only ONE by catching the super <code>Exception</code> excepton? or ...

How do you handle exceptions from API/library in your code?

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

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

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

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我有以下代码行：FileInfo dbFile = new FileInfo(fileName);dbFileSize = (long)dbFile.Length / 1024;//KBnew FileInfo(fileName)和dbFile.Length调用有8种可能的例外。我不能就这么无视他们。，我得抓住他们，。您将如何处理那些8异常？分开抓(太多行了)？只抓一个通过抓住超级Exceptio

问如何处理代码中API/库中的异常？
EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何处理代码中API/库中的异常？EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何处理代码中API/库中的异常？
EN