Databases
StackOverflow2013
Postsdbo
POHeader file best practices for typedefs
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHeader file best practices for typedefs
    primarykey
    data
    text
    <p>I'm using shared_ptr and STL extensively in a project, and this is leading to over-long, error-prone types like <code>shared_ptr&lt; vector&lt; shared_ptr&lt;const Foo&gt; &gt; &gt;</code> (I'm an ObjC programmer by preference, where long names are the norm, and still this is way too much.) It would be much clearer, I believe, to consistently call this <code>FooListPtr</code> and documenting the naming convention that "Ptr" means shared_ptr and "List" means vector of shared_ptr.</p> <p>This is easy to typedef, but it's causing headaches with the headers. I seem to have several options of where to define <code>FooListPtr</code>:</p> <ul> <li>Foo.h. That entwines all the headers and creates serious build problems, so it's a non-starter.</li> <li>FooFwd.h ("forward header"). This is what <em>Effective C++</em> suggests, based on iosfwd.h. It's very consistent, but the overhead of maintaining twice the number of headers seems annoying at best.</li> <li>Common.h (put all of them together into one file). This kills reusability by entwining a lot of unrelated types. You now can't just pick up one object and move it to another project. That's a non-starter.</li> <li>Some kind of fancy #define magic that typedef's if it hasn't already been typedefed. I have an abiding dislike for the preprocessor because I think it makes it hard for new people to grok the code, but maybe....</li> <li>Use a vector subclass rather than a typedef. This seems dangerous...</li> </ul> <p>Are there best practices here? How do they turn out in real code, when reusability, readability and consistency are paramount?</p> <p>I've marked this community wiki if others want to add additional options for discussion.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USRob Napier
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    2. 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. POHeader file best practices for typedefs
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POHeader file best practices for typedefs
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POHeader file best practices for typedefs
      1. This table or related slice is empty.
      1. VTUpMod
    1. COMay I ask why this question is a community wiki?
      singulars
      1. POHeader file best practices for typedefs
      1. USKonrad Rudolph
    2. CO@Konrad, if there were other proposals, I was suggesting adding them into the list to make it easier for later readers to see the various options separate from the answers on their merit. Perhaps community wiki is used differently?
      singulars
      1. POHeader file best practices for typedefs
      1. USRob Napier
    3. COAnd after more research I rediscovered what I discovered last time I clicked community wiki, which is that I didn't mean to do that... Hopefully I learned my lesson this time.
      singulars
      1. POHeader file best practices for typedefs
      1. USRob Napier
 

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