blocks|key|1247263|text|try用于运行可能引发异常的方法|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1247264|catch用于“捕捉”并停止该异常|1247265|finally用于捕获或未捕获该异常所需的任何清理工作|1247266|try{
++++myObject.riskyMethod();+//+run+a+method+that+may+throw+an+exception
}
catch(Exception+ex){
++++myLogger.log(ex.Message);+//+"catch"+stop+that+exception
}
finally{
++++myObject+=+null;+//+clean+up+needed+from+that+exception+being+caught
}|code-block|syntax|javascript|1247267|entityMap^0|0|3|0|0|5|0|0|7|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|T|8|@$9|U|A|V|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|J|3|K|5|L|7|Z|8|@]|D|@]|E|$M|N]]|$1|O|3|-4|5|6|7|10|8|@]|D|@]|E|$]]]|P|$]]

<code>try</code> is used to run a method that may throw an exception
<code>catch</code> is used to &quot;catch&quot; stop that exception
<code>finally</code> is used for any clean up needed from that exception being caught or not
<pre><code>try{
 myObject.riskyMethod(); // run a method that may throw an exception
}
catch(Exception ex){
 myLogger.log(ex.Message); // &quot;catch&quot; stop that exception
}
finally{
 myObject = null; // clean up needed from that exception being caught
}
</code></pre>

blocks|key|1032478|text|Finally和catch块有很大的不同：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1032479|在catch块中，您可以响应抛出的异常。仅当存在未处理的异常，并且类型与catch块的参数中指定的类型匹配或为该异常的子类时，才执行此块。最后，无论是否引发异常，都会在try和catch块之后执行。|1032480|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|$]]

Finally and catch blocks are quite different:

Within the catch block you can respond to the thrown exception. This block is executed only if there is an unhandled exception and the type matches the one or is subclass of the one specified in the catch block's parameter.
Finally will be always executed after try and catch blocks whether there is an exception raised or not.

blocks|key|1032394|text|在我的研究中，Finally块总是被执行的，它主要是“用于关闭任何打开的连接”，并销毁一些不必要的运行。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1032395|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In My reasearch Finally block is always executed and it is mainly "used for the any open connections to close" and to destroy something that is running unnecessarily.

blocks|key|1032546|text|通常，当我们使用流、连接等任何资源时。我们必须使用finally块显式地关闭它们。在下面给出的程序中，我们使用FileReader从文件中读取数据，并使用finally块关闭它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1032547|import+java.io.File;
import+java.io.FileReader;
import+java.io.IOException;

public+class+ReadData_Demo+{

+++public+static+void+main(String+args[]){
++++++FileReader+fr=null;+++++++
++++++try{
+++++++++File+file=new+File("file.txt");
+++++++++fr+=+new+FileReader(file);++char+[]+a+=+new+char[50];
+++++++++fr.read(a);+//+reads+the+content+to+the+array
+++++++++for(char+c+:+a)
+++++++++System.out.print(c);+//prints+the+characters+one+by+one
++++++}catch(IOException+e){
++++++++++e.printStackTrace();
+++++++}
+++++++finally{+
++++++++++try{
++++++++++++++fr.close();
++++++++++}catch(IOException+ex){+++++++
+++++++++++++++ex.printStackTrace();
+++++++++++}
+++++++}
++++}

}|code-block|syntax|javascript|1032548|也许其他像我这样的人也在搜索这样的东西。|1032549|来自此页面的信息tutpoint|offset|length|1032550|entityMap|0|LINK|mutability|MUTABLE|url|https://www.tutorialspoint.com/java/java_exceptions.htm^0|0|0|0|8|8|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|X|8|@]|9|@$K|Y|L|Z|1|10]]|A|$]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]]]

Generally when we use any resources like streams, connections etc.. we have to close them explicitly using finally block. In the program given below we are reading data from a file using FileReader and we are closing it using finally block.

<pre><code>import java.io.File;
import java.io.FileReader;
import java.io.IOException;

public class ReadData_Demo {

 public static void main(String args[]){
 FileReader fr=null; 
 try{
 File file=new File("file.txt");
 fr = new FileReader(file); char [] a = new char[50];
 fr.read(a); // reads the content to the array
 for(char c : a)
 System.out.print(c); //prints the characters one by one
 }catch(IOException e){
 e.printStackTrace();
 }
 finally{ 
 try{
 fr.close();
 }catch(IOException ex){ 
 ex.printStackTrace();
 }
 }
 }

}
</code></pre>

Maybe other guys like me searched for something like this.

Information from this page <a href="https://www.tutorialspoint.com/java/java_exceptions.htm" rel="nofollow">tutpoint</a>

blocks|key|1247319|text|最后，始终执行块。仅当捕获到与blocks参数匹配的异常时，才执行Catch块。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1247320|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Finally block is always executed. Catch block is executed only when an exception that matches the blocks parameter is catched.

blocks|key|1032303|text|即使在第一种形式中，您也可以将其记录在调用方法中。所以没有什么大的优势，除非你想在那里做一些特殊的处理。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1032304|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Even in the first form you could log it in the calling method. So there is no big advantage unless you want to do some special handling right there.

blocks|key|1032596|text|Try块将保存将要引发异常的语句。catch块将保存从try块抛出的引用，所需的消息是从catch块生成的。Finally块还用于关闭已使用的资源，如io关闭、文件关闭、dB关闭。在Java+-9增强的try-with资源中，资源是在try..in增强try+-+with资源之外声明的，catch块是强制的|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1032597|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Try block will hold the statements which are going to raise exception.
The catch block will hold the reference thrown from the try block and required messages are generated from catch block.
Finally block is also used to close the used resources like io closing,file closing, dB closing..
In Java -9 enhanced try-with resource came up where the resources are declared outside the try..in enchanced try with resource the catch block is mandatory

What's the difference between

<pre><code>try {
 fooBar();
} finally {
 barFoo();
}
</code></pre>

and

<pre><code>try {
 fooBar();
} catch(Throwable throwable) {
 barFoo(throwable); // Does something with throwable, logs it, or handles it.
}
</code></pre>

I like the second version better because it gives me access to the Throwable. Is there any logical difference or a preferred convention between the two variations?

Also, is there a way to access the exception from the finally clause?

Difference between try-finally and try-catch

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

两者的区别是什么try {    fooBar();} finally {    barFoo();}和try {  fooBar();} catch(Throwable throwable) {    barFoo(throwable); // Does something with throwable, logs it, or handles it.}我更喜欢第二个版本，因为它让我可以访问Th

问try-finally和try-catch之间的区别
EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问try-finally和try-catch之间的区别EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问try-finally和try-catch之间的区别
EN