Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The standard guarantees that static storage duration objects are initialized before any functions/variables in the same translation unit as your object are used from an external source.</p> <p>The wording here is designed to work with shared libraries. Because shared libraries can be dynamically loaded after main() has started the language specification has to be flexible enough to cope with it. But as long as you access your object from outside the translation unit then you are guaranteed that it will have been constructed before you are given accesses (unless you are doing something pathological).</p> <p><strong>BUT</strong> this does not stop it being used before initialization if it is used in the constructor of another static storage duration object in the same compilation unit.</p> <p>But you can easily manually provide guarantees that a static object is correctly initialized before used by using the technique below.</p> <p>Just change the static variable to a static function. Then inside the function declare a static member that is returned. So you can use it exactly the same way as before (just add <code>()</code>).</p> <pre><code>template &lt;class T&gt; struct PWrap_T { static P&amp; p_s(); // change static variable to static member function. // Rather than the type being P make it a reference to P // because the object will be held internally to the function }; template &lt;class T&gt; P&amp; PWrap_T&lt;T&gt;::p_s() { // Notice the member is static. // This means it will live longer than the function. // Also it will be initialized on first use. // and destructed when other static storage duration objects are destroyed. static P p_s_item(T::id(), T::desc()); return p_s_item; // Note its not guaranteed to be created before main(). // But it is guaranteed to be created before first use. } </code></pre> <p>So here you get the benefits of a global (whatever they are). You get guaranteed construction/destruction and you know the object will be correctly constructed before it can be used.</p> <p>The only change you need to make is:</p> <pre><code>void bar(int cnt) { for (int i = 0; i &lt; cnt; ++i) { PP(2, "description", pp); pp.p_s().doStuff(); // ^^ Add the braces here. } } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POnon-deferred static member initialization for templates in gcc?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMartin York
    1. USMartin York
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POnon-deferred static member initialization for templates in gcc?
      singulars
      1. PTQuestion
    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. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COOnly problem with this is that function-statics aren't threadsafe (the initialization of them, at least) in pre-C++11 iirc.
      singulars
      1. PO
      1. USBwmat
    2. CO@Bwmat: True the language does not guarantee it pre C++11. But gcc does (even pre C++11).
      singulars
      1. PO
      1. USMartin York
    3. CO@Bwmat: http://gcc.gnu.org/ml/gcc-patches/2004-09/msg00265.html
      singulars
      1. PO
      1. USMartin York
 

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