Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>If releasing some resource can actually <em>fail</em>, then a destructor is clearly a wrong abstraction to use. Destructors are meant to clean up without fail, regardless of the circumstances. A <code>close()</code> method (or whatever you want to name it) is probably the only way to go.</p> <p>But think closely about it. If releasing a resource actually <strong>fails</strong>, what can you do? Is such an error recoverable? If it is, which part of your code should handle it? The way to recover is probably highly application-specific and tied to other parts of the application. It is highly unlikely that you actually want that to happen <em>automatically</em>, in an arbitrary place in the code that happened to release the resource and trigger the error. A shared pointer abstraction does not really model what you're trying to achieve. If so, then you clearly need to create your own abstraction which models your requested behavior. Abusing shared pointers to do something they're not supposed to do is not the right way.</p> <p>Also, please read <a href="http://yosefk.com/c++fqa/exceptions.html#fqa-17.3" rel="nofollow noreferrer">this</a>.</p> <p><strong>EDIT:</strong><br> If all you want to do is to inform the user what happened before crashing, then consider wrapping the <code>Socket</code> in <em>another</em> wrapper object that would call the deleter on its destruction, catch any exceptions thrown and handle them by showing the user a message box or whatever. Then put this wrapper object inside a <code>boost::shared_ptr</code>.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to handle failure to release a resource which is contained in a smart pointer?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USslacker
    1. USslacker
    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. COIf releasing a resource fails, and the error is not recoverable, I need to at least report the problem to the user. All that is required for this is to throw an exception when the resource is released, and deal with it somewhere else in the code. This is no misuse of shared pointers.
      singulars
      1. PO
      1. UScj.
    2. COI am not using a destructor anywhere to indicate failure by throwing an exception. I am using a custom deleter function, which is not a destructor, and only when it is not called in the context of the shared pointer's destructor.
      singulars
      1. PO
      1. UScj.
    3. COThat is where you misuse the shared pointer. When you call release or ~ on a shared pointer the concept means that the resource behind it has been deleted if that caused the count to fall to 0. What you want goes beyond the boundaries of this concept. You simply need something smarter than shared pointers where ever designed to be.
      singulars
      1. PO
      1. USCrazy Eddie
 

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