Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>There is no guarantee that static members are destroyed only after all instances of an object of the same class. C++ incorporates no reference counting paradigm (<code>shared_ptr</code> notwithstanding).</p> <p>When considering lifetime, consider your static members as any other static object. There's really nothing binding them to their containing class other than being in the class's "namespace" (<em>warning: not accurate terminology</em>).</p> <p>So, if your <code>myClass</code> instances are created statically too, then you need to consider normal static object lifetime rules between them:</p> <p><a href="http://www.ideone.com/ig5rU" rel="nofollow">Example #1</a>:</p> <pre><code>#include &lt;iostream&gt; struct A { A() { std::cout &lt;&lt; "*A "; }; ~A() { std::cout &lt;&lt; "~A "; }; }; struct B { B() { std::cout &lt;&lt; "*B "; }; ~B() { std::cout &lt;&lt; "~B "; }; static A a; }; B t; A B::a; int main() {} // Output: *B *A ~A ~B </code></pre> <p>As you can see, the static member of <code>B</code> is destroyed before the actual instance of <code>B</code>.</p> <p><a href="http://www.ideone.com/mhIO1" rel="nofollow">Example #2:</a></p> <pre><code>#include &lt;iostream&gt; struct A { A() { std::cout &lt;&lt; "*A "; }; ~A() { std::cout &lt;&lt; "~A "; }; }; struct B { B() { std::cout &lt;&lt; "*B "; }; ~B() { std::cout &lt;&lt; "~B "; }; static A a; }; A B::a; B t; int main() {} // Output: *A *B ~B ~A </code></pre> <p>Here the reverse is true. It's a cheap fix for your current issue, but my advice is to avoid static instances altogether; you'll only fall into more static initialisation pitfalls like this down the line... possibly with a future incarnation of the same code!</p>
    singulars
    1. This table or related slice is empty.
    1. POStatic members being destroyed while there are still outstanding instances?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USLightness Races in Orbit
    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
    1. COThis will only happen to global objects and only when the program ends. That an object is encapsulated as an static object in another namespace doesn't change the fact that it is basically a global object
      singulars
      1. PO
      1. USGunther Piez
    2. CO@drhirsch: I just said all that! (Your use of "global" is not right, though.)
      singulars
      1. PO
      1. USLightness Races in Orbit
    3. COWell yes :-) But I thought it is was not relevant, because I couldn't imagine the OP would use a global MyClass, possibly create a static member after the global MyClass and then ask why he gets problems accessing a static member... Now I am not so sure anymore ;-)
      singulars
      1. PO
      1. USGunther Piez
 

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