Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <blockquote> <p>If an exception is thrown during execution of a finally block, and an exception was already being propagated, that exception is lost</p> </blockquote> <p>Basically, what's happening when you execute:</p> <ul> <li><code>CryptographicException</code> is thrown in inner finally.</li> <li>Outer-scope finally executes, and throws <code>ArgumentException</code>. Since "CryptographicException" was "being propogated" at this point in time, it is lost.</li> <li>Final catches occur, and <code>ArgumentException</code> is caught.</li> </ul> <blockquote> <p>... and it wouldn't make sense for the first exception to simply disappear into the ether, just because there was another exception thrown from a different finally block.</p> </blockquote> <p>This is exactly what happens, based on the C# language specification you quoted. The first exception (<code>CryptographicException</code>) effectively disappears - it's "lost". </p> <p>You can only reach this state by explicitly using <code>finally</code>, though, so I believe the assumption is that you're providing the error handling with this expectation or possibility in mind (as you're using <code>try</code> at that point, which means you've accepted you may have an exception).</p> <p>This is basically explained in detail in the spec in <code>8.9.5</code> (the text in <code>8.10</code> you quoted refers to this section):</p> <blockquote> <p>If the finally block throws another exception, processing of the current exception is terminated. </p> </blockquote> <p>The first exception, in your case the <code>ArgumentException</code>, basically "disappears".</p>
    singulars
    1. This table or related slice is empty.
    1. POCatch block is not being evaluated when exceptions are thrown from finallys
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USReed Copsey
    1. USReed Copsey
    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. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COYou can reach this state with a `try`/`catch`/`finally` as well, if the first exception leaves the catch.
      singulars
      1. PO
      1. USBAF
    2. CO@BAF Yes - I was more trying to say that you *must* have a try with a finally (you can have a catch in there, too). try/catch or lack of any "try" isn't enough. I reworded - is that more clear?
      singulars
      1. PO
      1. USReed Copsey
    3. COAh, alright. I guess the wording was slightly confusing to me then; seemed like you were saying the only way to have this happen is with `try`/`finally`.
      singulars
      1. PO
      1. USBAF
 

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