我听到过的最好的建议是，您应该只在可以对异常条件采取措施的情况下捕获异常，而“捕获、记录和释放”并不是一个好策略(如果在库中偶尔不可避免的话)。

我听到过的最好的建议是，您应该只在可以对异常条件采取措施的情况下捕获异常，而“捕获、记录和释放”并不是一个好策略(如果在库中偶尔不可避免的话)。

您不需要在try-catch中掩盖代码的每一部分。try-catch块的主要用途是错误处理和获取程序中的错误/异常。try-catch -的用法

您可以在想要处理异常的地方使用此块，或者简单地说编写的代码块可能抛出异常。 如果你想在对象使用后立即释放它们，你可以使用try-catch块。

我的计算机科学教授曾经给我的建议是:“只有在使用标准方法无法处理错误时，才使用Try and Catch块。”

作为一个例子，他告诉我们，如果一个程序在一个地方遇到了一些严重的问题，而不可能做这样的事情:

int f()
{
    // Do stuff

    if (condition == false)
        return -1;
    return 0;
}

int condition = f();

if (f != 0)
{
    // handle error
}

然后你应该使用try, catch块。虽然您可以使用异常来处理这个问题，但通常不建议这样做，因为异常会消耗大量性能。

As Mitch and others stated, you shouldn't catch an exception that you do not plan on handling in some way. You should consider how the application is going to systematically handle exceptions when you are designing it. This usually leads to having layers of error handling based on the abstractions - for example, you handle all SQL-related errors in your data access code so that the part of the application that is interacting with domain objects is not exposed to the fact that there is a DB under the hood somewhere.

除了“在任何地方捕获所有东西”的味道之外，还有一些相关的代码味道是您一定要避免的。

"catch, log, rethrow": if you want scoped based logging, then write a class that emits a log statement in its destructor when the stack is unrolling due to an exception (ala std::uncaught_exception()). All that you need to do is declare a logging instance in the scope that you are interested in and, voila, you have logging and no unnecessary try/catch logic. "catch, throw translated": this usually points to an abstraction problem. Unless you are implementing a federated solution where you are translating several specific exceptions into one more generic one, you probably have an unnecessary layer of abstraction... and don't say that "I might need it tomorrow". "catch, cleanup, rethrow": this is one of my pet-peeves. If you see a lot of this, then you should apply Resource Acquisition is Initialization techniques and place the cleanup portion in the destructor of a janitor object instance.

我认为充斥着try/catch块的代码是代码评审和重构的好目标。它表明要么异常处理没有被很好地理解，要么代码已经变成了无用的，急需重构。

正如在其他回答中所述，只有在可以对异常进行某种合理的错误处理时才应该捕获异常。

例如，在生成您的问题的问题中，提问者询问忽略从整数到字符串的lexical_cast异常是否安全。这样的阵容永远不会失败。如果它失败了，说明程序中出现了严重的错误。在这种情况下，你能做些什么来恢复呢?最好的方法可能是让程序死亡，因为它处于不可信任的状态。因此，不处理异常可能是最安全的做法。