Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I've finally understood what the problem was... and your solution does not solve much, if any.</p> <p>The goal of using local static variable is to provide initialization on first use, thus being safe from the "Initialization Order Fiasco" (by the way, it does not solve the "Destruction Order Fiasco").</p> <p>But with your design, if you effectively prevent the <code>crash</code> you do not however prevent the issue of using a variable before its value is used.</p> <pre><code>ImportantObject&lt;tbt&gt; SinceSliceBread; // using an empty string tbt::set_name("xyz"); </code></pre> <p>Compare with the following use:</p> <pre><code>std::string&amp; tbt::get_name() { static std::string MName = "xyz"; return MName; } </code></pre> <p>Here the <code>name</code> is not only created but also <strong>initialized</strong> on first use. What's the point of using a non initialized name ?</p> <p>Well, now that we know your solution does not work, let's think a bit. In fact we would like to automate this:</p> <pre><code>struct tag { static const std::string&amp; get_name(); static const std::string&amp; get_fs_location(); }; </code></pre> <p>(with possibly some accessors to modify them)</p> <p>My first (and easy) solution would be to use a macro (bouh not typesafe):</p> <pre><code>#define DEFINE_NEW_TAG(Tag_, Name_, FsLocation_) \ struct Tag_ \ { \ static const std::string&amp; get_name() { \ static const std::string name = #Name_; \ return name; \ } \ static const std::string&amp; get_fs_location() { \ static const std::string fs_location = #FsLocation_; \ return fs_location; \ } \ }; </code></pre> <p>The other solution, in your case, could be to use <code>boost::optional</code> to detect that the value has not been initialized yet, and postpone initialization of the values that depend on it.</p>
    singulars
    1. This table or related slice is empty.
    1. POCompile time Meta-programming, with string literals
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USMatthieu M.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POCompile time Meta-programming, with string literals
      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
    1. COYes, I have not addressed the issue of initialization sequencing, My main concern was to have an easy way to use strings which are available at compile time and associate them with a compile time tag. Boost::MPI string literals are a bit of a hack and c++0x is addressing the issue. so, I chose the static-string-declared-in-function technique from Myers' book. Thank you for the analysis, and your Macro can certainly make the code read more like a story.
      singulars
      1. PO
      1. USHassan Syed
    2. COAccepted as answer, as it adds value to the question. However, a lot of people have discussed this question and I have made successive edits to the code in the question. Boost optional is a very good way of guarding against initialization issues. Perhaps I will add it, however since the code is for internal use in my project I might not do it immediately.
      singulars
      1. PO
      1. USHassan Syed
 

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