blocks|key|5852950|text|JavaDocs很好地总结了这些内容。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5852951|java.lang.RuntimeException|offset|length|style|CODE|5852952|Java是这些异常的超类，这些异常可以在|5852953|虚拟机的正常操作期间抛出。|blockquote|5852954|5852955|方法不需要在其throws子句中声明在方法执行期间可能抛出但未被捕获的RuntimeException的任何子类。|5852956|5852957|java.lang.Error|5852958|Throwable+An+Error是|5852959|的子类，表示合理的应用程序不应尝试捕获的严重问题。大多数这样的错误都是异常情况。虽然ThreadDeath错误是一种“正常”情况，但它也是错误的一个子类，因为大多数应用程序都不应该尝试捕获它。|5852960|5852961|方法不需要在其throws子句中声明在方法执行期间可能抛出但未被捕获的错误的任何子类，因为这些错误是不应该发生的异常情况。|5852962|5852963|请注意，“未检查的异常”只是RuntimeException的同义词。|5852964|entityMap|0|LINK|mutability|MUTABLE|url|http://java.sun.com/javase/6/docs/api/java/lang/RuntimeException.html|1|http://java.sun.com/javase/6/docs/api/java/lang/Error.html^0|0|0|Q|0|Q|0|0|0|0|0|0|0|0|F|0|F|1|0|0|0|0|0|0|E|G|0^^$0|@$1|2|3|4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1D|8|@$D|1E|E|1F|F|G]]|9|@$D|1G|E|1H|1|1I]]|A|$]]|$1|H|3|I|5|6|7|1J|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|1K|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|1L|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|1M|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|1N|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1O|8|@$D|1P|E|1Q|F|G]]|9|@$D|1R|E|1S|1|1T]]|A|$]]|$1|S|3|T|5|6|7|1U|8|@]|9|@]|A|$]]|$1|U|3|V|5|L|7|1V|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1W|8|@]|9|@]|A|$]]|$1|X|3|Y|5|6|7|1X|8|@]|9|@]|A|$]]|$1|Z|3|-4|5|6|7|1Y|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|1Z|8|@$D|20|E|21|F|G]]|9|@]|A|$]]|$1|12|3|-4|5|6|7|22|8|@]|9|@]|A|$]]]|13|$14|$5|15|16|17|A|$18|19]]|1A|$5|15|16|17|A|$18|1B]]]]

The JavaDocs sum these up pretty well.
<a href="http://java.sun.com/javase/6/docs/api/java/lang/RuntimeException.html" rel="noreferrer"><code>java.lang.RuntimeException</code></a>:
<blockquote>
RuntimeException is the superclass of those exceptions that can be thrown during the normal operation of the Java Virtual Machine.
A method is not required to declare in its throws clause any subclasses of RuntimeException that might be thrown during the execution of the method but not caught.
</blockquote>
<a href="http://java.sun.com/javase/6/docs/api/java/lang/Error.html" rel="noreferrer"><code>java.lang.Error</code></a>:
<blockquote>
An Error is a subclass of Throwable that indicates serious problems that a reasonable application should not try to catch. Most such errors are abnormal conditions. The ThreadDeath error, though a &quot;normal&quot; condition, is also a subclass of Error because most applications should not try to catch it.
A method is not required to declare in its throws clause any subclasses of Error that might be thrown during the execution of the method but not caught, since these errors are abnormal conditions that should never occur.
</blockquote>
Note that &quot;unchecked exception&quot; is merely a synonym for a <code>RuntimeException</code>.

blocks|key|2324168|text|RuntimeExceptions和像OutOfMemoryError这样的错误不需要被捕获，它们可以抛出，直到它们到达main()，这将终止应用程序。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2324169|如果其他异常未被捕获或未包括在抛出列表中，则会导致编译错误。|2324170|entityMap^0|0|H|J|G|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|P|8|@]|D|@]|E|$]]]|I|$]]

<code>RuntimeExceptions</code> and Errors like <code>OutOfMemoryError</code> don't need to be catched and can be thrown until they reach main() which will terminate the application.

Other Exceptions cause an compile error if they are not catched or included in the throws list.

blocks|key|4436987|text|注意:+RuntimeException是一个未检查的异常|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4436988|未检查的异常是已知在执行过程中的某个点可能发生但未被捕获的异常，例如，如果您不检查它们，则总是有可能出现NullPointerException，这将导致程序终止。您可以通过在try-catch中包装代码来检查它，但这不是强制的(与强制以某种方式处理异常的受控异常不同)。|4436989|错误是在执行过程中的任何时刻都可能发生的错误，并且不能真正被捕获，因为它不是由特定的方法调用等明确导致的。例如，OutOfMemoryError或StackOverflowError。这两种情况随时都可能发生，并会导致您的应用程序终止。捕获这些错误没有任何意义，因为它们表明发生了一些您无法恢复的事情。|4436990|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|$]]

Note: a RuntimeException IS an unchecked exception

An unchecked exception would be one that is known to be possible at a point in the execution but is not caught, for example a NullPointerException is always a possibility if you don't check for them and will cause your program to terminate. You could check for it by wrapping code in try-catch, but this is not enforced (unlike a checked exception that will enforce that the exception is handled in some way).

An error is something that can occur at any point during execution and can't really be caught because it is not eplicitly caused by a particular method call etc. For example an OutOfMemoryError or a StackOverflowError. Both of these could occur at any time and will cause your application to terminate. Catching these errors make no sense as they indicate that something has happened that you won't be able to recover from.

blocks|key|1782913|text|Errors指示不应该发生的基本问题。如果你遇到一个错误的s.th。非常糟糕的事情发生了。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1782914|另一方面，未检查异常(运行时异常)在任何可能出现异常，但没有合理的方法处理它时使用，因此try+catch语句将非常烦人且浪费空间。|1782915|entityMap^0|0|6|0|5|5|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|P|8|@]|D|@]|E|$]]]|I|$]]

Errors indicate fundamental problems that should never occur. If you run into an error s.th. really bad happened. 
Unchecked Exceptions (Runtime Exceptions) on the other hand are used whenever an exception could be expected somehow but there is no reasonable way to deal with it then and thus a try catch statement would be just annoying and a waste of space.

blocks|key|4437109|text|顾名思义，未检查的异常是在编译时时不检查的，这意味着编译器不需要方法来捕获或指定(使用throws)它们。属于此类别的类在JLS的11.2+Compile-Time+Checking+of+Exceptions小节中有详细介绍：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4437110|RuntimeException+Error类<+|BOLD|4437111|+>E119>及其子类<>E220>。所有其他异常类都是选中的异常类。Java+API定义了许多异常类，包括选中的和未选中的。附加的异常类，包括选中的和未选中的，都可以由程序员声明。有关异常类层次结构和Java+API和Java虚拟机定义的一些异常类的描述，请参阅§11.5。|blockquote|4437112|4437113|4437114|下图说明了异常层次结构：|4437115|​|4437116|📷|atomic|4437117|4437118|类Error及其子类是异常，通常不希望普通程序从这些异常中恢复，如11.5+The+Exception+Hierarchy中所述|4437119|4437120|类Error是Throwable的一个单独的子类，在类层次结构中与Exception不同，它允许程序使用以下习惯用法：|4437121|4437122|}+catch+(异常e)+{|4437123|捕获所有可能恢复的异常，而不捕获通常无法恢复的错误。|4437124|4437125|总而言之，RuntimeException是可以恢复的异常的未检查异常的子集(但未检查异常不是RuntimeException的同义词，因为许多人在这里回答)。|4437126|entityMap|0|LINK|mutability|MUTABLE|url|http://java.sun.com/docs/books/jls/second_edition/html/exceptions.doc.html#44121|1|http://java.sun.com/docs/books/jls/second_edition/html/exceptions.doc.html#44278|2|IMAGE|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/a7070582125b5f82a53cd4fb13a116bf.gif|imageAlt|3^0|17|6|1T|14|0|0|0|G|H|5|0|G|H|5|0|3O|5|1|0|0|0|0|0|0|1|2|0|0|1|5|X|S|3|0|0|1|5|7|9|X|9|0|0|0|0|0|5|G|1B|G|0^^$0|@$1|2|3|4|5|6|7|1P|8|@$9|1Q|A|1R|B|C]]|D|@$9|1S|A|1T|1|1U]]|E|$]]|$1|F|3|G|5|6|7|1V|8|@$9|1W|A|1X|B|H]|$9|1Y|A|1Z|B|H]|$9|20|A|21|B|C]|$9|22|A|23|B|C]]|D|@]|E|$]]|$1|I|3|J|5|K|7|24|8|@]|D|@$9|25|A|26|1|27]]|E|$]]|$1|L|3|-4|5|6|7|28|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|29|8|@]|D|@]|E|$]]|$1|N|3|O|5|6|7|2A|8|@]|D|@]|E|$]]|$1|P|3|Q|5|6|7|2B|8|@]|D|@]|E|$]]|$1|R|3|S|5|T|7|2C|8|@]|D|@$9|2D|A|2E|1|2F]]|E|$]]|$1|U|3|Q|5|6|7|2G|8|@]|D|@]|E|$]]|$1|V|3|W|5|6|7|2H|8|@$9|2I|A|2J|B|C]]|D|@$9|2K|A|2L|1|2M]]|E|$]]|$1|X|3|-4|5|6|7|2N|8|@]|D|@]|E|$]]|$1|Y|3|Z|5|K|7|2O|8|@$9|2P|A|2Q|B|C]|$9|2R|A|2S|B|C]|$9|2T|A|2U|B|C]]|D|@]|E|$]]|$1|10|3|-4|5|6|7|2V|8|@]|D|@]|E|$]]|$1|11|3|12|5|6|7|2W|8|@]|D|@]|E|$]]|$1|13|3|14|5|6|7|2X|8|@]|D|@]|E|$]]|$1|15|3|-4|5|6|7|2Y|8|@]|D|@]|E|$]]|$1|16|3|17|5|6|7|2Z|8|@$9|30|A|31|B|C]|$9|32|A|33|B|C]]|D|@]|E|$]]|$1|18|3|-4|5|6|7|34|8|@]|D|@]|E|$]]]|19|$1A|$5|1B|1C|1D|E|$1E|1F]]|1G|$5|1B|1C|1D|E|$1E|1H]]|1I|$5|1J|1C|1K|E|$1L|1M|1N|-4]]|1O|$5|1B|1C|1D|E|$1E|1H]]]]

As stated by their name, unchecked exceptions are not checked at compile-time which means that the compiler doesn't require methods to catch or to specify (with a <code>throws</code>) them. Classes belonging to this category are detailed in the section <a href="http://java.sun.com/docs/books/jls/second_edition/html/exceptions.doc.html#44121" rel="noreferrer">11.2 Compile-Time Checking of Exceptions</a> of the JLS:

<blockquote>
 The unchecked exceptions classes are the class <code>RuntimeException</code> and its subclasses, and the class <code>Error</code> and its subclasses. All other exception classes are checked exception classes. The Java API defines a number of exception classes, both checked and unchecked. Additional exception classes, both checked and unchecked, may be declared by programmers. See <a href="http://java.sun.com/docs/books/jls/second_edition/html/exceptions.doc.html#44278" rel="noreferrer">§11.5</a> for a description of the exception class hierarchy and some of the exception classes defined by the Java API and Java virtual machine.
</blockquote>

The following picture illustrates the Exception hierarchy:

<img src="https://www.artima.com/javaseminars/modules/images/Checked.gif" alt="alt text">

The class <code>Error</code> and its subclasses are exceptions from which ordinary programs are not ordinarily expected to recover and, as explained in <a href="http://java.sun.com/docs/books/jls/second_edition/html/exceptions.doc.html#44278" rel="noreferrer">11.5 The Exception Hierarchy</a>:

<blockquote>
 The class <code>Error</code> is a separate
 subclass of <code>Throwable</code>, distinct from
 <code>Exception</code> in the class hierarchy, to
 allow programs to use the idiom:

<pre><code>} catch (Exception e) {
</code></pre>
 
 to catch all exceptions from which
 recovery may be possible without
 catching errors from which recovery is
 typically not possible.
</blockquote>

To summarize, <code>RuntimeException</code> are a subset of unchecked exceptions for exceptions from which recovery is possible (but unchecked exception is not a synonym of <code>RuntimeException</code> as many are answering here).

blocks|key|4437165|text|错误和运行时异常统称为未检查异常。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4437166|运行时异常是应用程序内部的异常情况，应用程序通常无法预期或从中恢复。这些通常表示编程错误，如逻辑错误或API使用不当|4437167|您可能想看看这个链接，它解释了三种类型的异常。|4437168|http://docs.oracle.com/javase/tutorial/essential/exceptions/catchOrDeclare.html|offset|length|4437169|我希望这能帮到你。|4437170|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|0|27|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|U|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|V|8|@]|9|@$H|W|I|X|1|Y]]|A|$]]|$1|J|3|K|5|6|7|Z|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|G]]]]

Errors and runtime exceptions are collectively known as unchecked exceptions.

runtime exceptions are exceptional conditions that are internal to the application, and that the application usually cannot anticipate or recover from. These usually indicate programming bugs, such as logic errors or improper use of an API

You may want to take a look at this link which explains the Three Kinds of Exceptions.

<a href="http://docs.oracle.com/javase/tutorial/essential/exceptions/catchOrDeclare.html" rel="nofollow">http://docs.oracle.com/javase/tutorial/essential/exceptions/catchOrDeclare.html</a>

I hope this helps.

blocks|key|2324371|text|Error：这些异常情况是应用程序的外部异常()，应用程序通常无法预料到这些情况或从中恢复。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2324372|运行时异常状态(Runtime+exception+)：这些异常状态是应用程序的内部，应用程序通常无法预期或从中恢复。|2324373|您可能想要阅读this：|2324374|entityMap|0|LINK|mutability|MUTABLE|url|http://docs.oracle.com/javase/tutorial/essential/exceptions/catchOrDeclare.html^0|0|5|0|0|P|14|2|0|7|4|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|Z|8|@]|D|@$9|10|A|11|1|12]]|E|$]]|$1|J|3|-4|5|6|7|13|8|@]|D|@]|E|$]]]|K|$L|$5|M|N|O|E|$P|Q]]]]

Error: These are exceptional conditions that are external to the application, and that the application usually cannot anticipate or recover from.

Runtime exception : These are exceptional conditions that are internal to the application, and that the application usually cannot anticipate or recover from.

You may want to read <a href="http://docs.oracle.com/javase/tutorial/essential/exceptions/catchOrDeclare.html" rel="nofollow">this</a> :

blocks|key|1779672|text|已检查异常：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1779673|1779674|除了RuntimeException和Error之外，扩展Throwable类的类称为检查异常。|unordered-list-item|CODE|1779675|也称为编译时异常，因为这些类型的异常是在编译时检查的。这意味着如果我们忽略这些异常(没有用try/catch或throw处理异常)，那么就会发生编译错误。|1779676|它们是可通过编程方式恢复的问题，这些问题是由代码控制之外的意外情况(例如，数据库宕机、文件I/O错误、错误输入等)导致的。|1779677|我们可以使用try/catch+etc+IOException、SQLException+|1779678|来避免这些问题|1779679|未检查异常：|1779680|1779681|扩展RuntimeException的类称为未检查异常|1779682|未检查异常在编译时不被检查，而是在runtime.And检查它们也称为“运行时异常”|1779683|它们也是可编程恢复的问题，但与<代码>E133已检查异常<代码>E234不同，它们是由代码流或configuration.|1779684|Example:中的错误引起的<代码>D37，<代码>D38，<代码>D39+etc+<代码>H240<代码>H141由于它们是编程错误，可以通过良好/明智的编码避免。例如，“除以零”发生在ArithmeticEceeption上。我们可以通过一个简单的if条件-+if(divisor!=0)来避免它们。类似地，我们可以通过简单地检查引用-+NullPointerException或者甚至使用if(object!=null)来避免if(object!=null)|1779685|1779686|错误：|1779687|1779688|Error指的是try/catch+|1779689|未处理的不可恢复的情况示例：OutOfMemoryError、VirtualMachineError、AssertionError等|1779690|1779691|entityMap^0|3|3|0|0|2|G|J|5|T|9|0|19|9|1J|5|0|0|6|9|K|B|W|C|0|0|0|6|0|0|2|G|0|Z|7|0|0|2N|J|3P|E|4S|K|5I|G|61|G|0|0|0|3|0|0|0|5|0|E|G|V|J|1F|E|0|0^^$0|@$1|2|3|4|5|6|7|1E|8|@$9|1F|A|1G|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|1H|8|@]|D|@]|E|$]]|$1|G|3|H|5|I|7|1I|8|@$9|1J|A|1K|B|J]|$9|1L|A|1M|B|J]|$9|1N|A|1O|B|J]]|D|@]|E|$]]|$1|K|3|L|5|I|7|1P|8|@$9|1Q|A|1R|B|J]|$9|1S|A|1T|B|J]]|D|@]|E|$]]|$1|M|3|N|5|I|7|1U|8|@]|D|@]|E|$]]|$1|O|3|P|5|I|7|1V|8|@$9|1W|A|1X|B|J]|$9|1Y|A|1Z|B|J]|$9|20|A|21|B|J]]|D|@]|E|$]]|$1|Q|3|R|5|6|7|22|8|@]|D|@]|E|$]]|$1|S|3|T|5|6|7|23|8|@$9|24|A|25|B|C]]|D|@]|E|$]]|$1|U|3|-4|5|6|7|26|8|@]|D|@]|E|$]]|$1|V|3|W|5|I|7|27|8|@$9|28|A|29|B|J]]|D|@]|E|$]]|$1|X|3|Y|5|I|7|2A|8|@$9|2B|A|2C|B|C]]|D|@]|E|$]]|$1|Z|3|10|5|I|7|2D|8|@]|D|@]|E|$]]|$1|11|3|12|5|I|7|2E|8|@$9|2F|A|2G|B|J]|$9|2H|A|2I|B|J]|$9|2J|A|2K|B|J]|$9|2L|A|2M|B|J]|$9|2N|A|2O|B|J]]|D|@]|E|$]]|$1|13|3|-4|5|6|7|2P|8|@]|D|@]|E|$]]|$1|14|3|15|5|6|7|2Q|8|@$9|2R|A|2S|B|C]]|D|@]|E|$]]|$1|16|3|-4|5|6|7|2T|8|@]|D|@]|E|$]]|$1|17|3|18|5|I|7|2U|8|@$9|2V|A|2W|B|J]]|D|@]|E|$]]|$1|19|3|1A|5|I|7|2X|8|@$9|2Y|A|2Z|B|J]|$9|30|A|31|B|J]|$9|32|A|33|B|J]]|D|@]|E|$]]|$1|1B|3|-4|5|6|7|34|8|@]|D|@]|E|$]]|$1|1C|3|-4|5|6|7|35|8|@]|D|@]|E|$]]]|1D|$]]

Checked Exception:

<ul>
<li>The classes that extend <code>Throwable</code> class except <code>RuntimeException</code> and <code>Error</code> are known as checked exceptions. </li>
<li>Also known as compile time exception because these type of exceptions are checked at compile time. That means if we ignore these exception (not handled with <code>try/catch</code> or <code>throw</code> the exception) then a compilation error occurred. </li>
<li>They are programmatically recoverable problems which are caused by unexpected conditions outside control of code (e.g. database down, file I/O error, wrong input, etc)</li>
<li>We can avoid them using <code>try/catch</code> block.</li>
<li>Example: <code>IOException</code>, <code>SQLException</code> etc </li>
</ul>

Unchecked Exception:

<ul>
<li>The classes that extend <code>RuntimeException</code> are known as unchecked exceptions </li>
<li>Unchecked exceptions are not checked at compile-time rather they are checked at runtime.And thats why they are also called "Runtime Exception" </li>
<li>They are also programmatically recoverable problems but unlike checked exception they are caused by faults in code flow or configuration.</li>
<li>Example: <code>ArithmeticException</code>,<code>NullPointerException</code>, <code>ArrayIndexOutOfBoundsException</code> etc </li>
<li>Since they are programming error, they can be avoided by nicely/wisely coding. For example "dividing by zero" occurs <code>ArithmeticEceeption</code>. We can avoid them by a simple if condition - <code>if(divisor!=0)</code>. Similarly we can avoid <code>NullPointerException</code> by simply checking the references - <code>if(object!=null)</code> or using even <a href="http://javarevisited.blogspot.com/2013/05/ava-tips-and-best-practices-to-avoid-nullpointerexception-program-application.html" rel="nofollow">better techniques</a></li>
</ul>

Error: 

<ul>
<li><code>Error</code> refers irrecoverable situation that are not being handled by try/catch </li>
<li>Example: <code>OutOfMemoryError</code>, <code>VirtualMachineError</code>, <code>AssertionError</code> etc.</li>
</ul>

This was an interview question. What is the main difference between unchecked exception and error as both are not caught? They will terminate the program.

Difference between Unchecked exception or runtime exception

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

这是一个面试问题。未检查的异常和错误之间的主要区别是什么，因为两者都没有被捕获？他们会终止这个程序。

问未检查异常与运行时异常的区别
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问未检查异常与运行时异常的区别EN