Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The designers of the language simply didn't want to (or couldn't) reason about the semantics of a finally block being terminated by a control transfer.</p> <p>One issue, or perhaps the key issue, is that the <code>finally</code> block gets executed as part of some non-local control transfer (exception processing). The target of that control transfer isn't the enclosing loop; the exception processing aborts the loop and continues unwinding further.</p> <p>If we have a control transfer out of the <code>finally</code> cleanup block, then the original control transfer is being "hijacked". It gets canceled, and control goes elsewhere.</p> <p>The semantics can be worked out. Other languages have it.</p> <p>The designers of C# decided to simply disallow static, "goto-like" control transfers, thereby simplifying things somewhat.</p> <p>However, even if you do that, it doesn't solve the question of what happens if a dynamic transfer is initiated from a <code>finally</code>: what if the finally block calls a function, and that function throws? The original exception processing is then "hijacked".</p> <p>If you work out the semantics of this second form of hijacking, there is no reason to banish the first type. They are really the same thing: a control transfer is a control transfer, whether it the same lexical scope or not.</p>
    singulars
    1. This table or related slice is empty.
    1. POWhy can't a 'continue' statement be inside a 'finally' block?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USKaz
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTDownMod
    1. COThe difference is that `finally` by definition *must* be immediately followed by continuing the transfer that triggered it (an uncaught exception, `return`, etc.). It would be easy to allow "goto-like" transfers within `finally` (which languages do this, by the way?), but doing so would mean that `try { return } finally { ... }` *may not return*, which is completely unexpected. If `finally` calls a function that throws, that's not really the same thing, because we already expect that exceptions may occur at any time and interrupt normal flow.
      singulars
      1. PO
      1. USnmclean
    2. CO@nmclean: Actually, an exception which escapes `finally` is sorta same thing, in that it can result in unexpected and illogical program flow. The only difference is that the language designers, being unable to reject all programs where a finally block could throw an unhandled exception, instead allow such programs to compile and hope the program can accept any consequences that may follow the abandonment of the earlier exception-unwinding sequence.
      singulars
      1. PO
      1. USsupercat
    3. CO@supercat I agree that it breaks expected flow, but my point is that that is *always* the case for unhandled exceptions, whether the current flow is a `finally` or not. By the logic of Kaz's last paragraph, functions should also be free to affect the flow in their caller's scope by way of `continue` etc., because they are allowed to do so by way of exceptions. But this of course is not allowed; exceptions are the *sole* exception to this rule, hence the name "exception" (or "interrupt").
      singulars
      1. PO
      1. USnmclean
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload