Databases
StackOverflow2013
Postsdbo
POSingleton with finalizer but not IDisposable
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSingleton with finalizer but not IDisposable
    primarykey
    data
    text
    <p>This is what I understand about IDisposable and finalizers from "CLR via C#", "Effective C#" and other resources:</p> <ul> <li>IDisposable is for cleaning up managed and unmanaged resources deterministically.</li> <li>Classes that are responsible for unmanaged resources (e.g. file handles) should implement IDisposable and provide a finalizer to guarantee that they are cleaned up even if the client code does not call Dispose() on the instance. </li> <li>Classes that are responsible for managed resources only should never implement a finalizer.</li> <li>If you have a finalizer then you must implement IDisposable (this allows client code to do the right thing and call Dispose(), while the finalizer prevents leaking resources if they forget).</li> </ul> <p>While I understand the reasoning for and agree with all of the above, there is one scenario where I think it makes sense to break these rules: a singleton class that is responsible for unmanaged resources (such as providing a single point of access to particular files).</p> <p>I believe it is always wrong to have a Dispose() method on a singleton because the singleton instance should live for the life of the application and if any client code calls Dispose() then you are stuffed. However, you want a finalizer so that when the application is unloaded the finalizer can clean up the unmanaged resources.</p> <p>So having a singleton class with a finalizer that does not implement IDisposable seems to me to be a reasonable thing to do, yet this type of design is counter to what I understand are best practices.</p> <p>Is this a reasonable approach? If not, why not and what are the superior alternatives?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USBen Robbins
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POSingleton with finalizer but not IDisposable
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POSingleton with finalizer but not IDisposable
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POSingleton with finalizer but not IDisposable
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

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