Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Does something like this fit the bill?</p> <pre><code>class W {}; class X {}; class Y {}; class Z : public X, public Y {}; template &lt;typename A, typename B&gt; class DualPointer { public: template &lt;typename T&gt; DualPointer(T *t) : a_ptr_(t), b_ptr_(t) {} operator A*() { return a_ptr_; } operator B*() { return b_ptr_; } private: A *a_ptr_; B *b_ptr_; }; int main() { Z z; DualPointer&lt;X, Y&gt; p(&amp;z); X *x = p; Y *y = p; return 0; } </code></pre> <p>Or if you're in a C++11 mood:</p> <pre><code>template &lt;typename... Ts&gt; class MultiPointer; template &lt;typename T, typename... Rest&gt; class MultiPointer&lt;T, Rest...&gt; : public MultiPointer&lt;Rest...&gt; { public: template &lt;typename U&gt; MultiPointer(U *u) : MultiPointer&lt;Rest...&gt;(u), ptr_(u) {}; operator T*() { return ptr_; } private: T *ptr_; }; template &lt;&gt; class MultiPointer&lt;&gt; { public: MultiPointer(void *) {} }; int main() { Z z; MultiPointer&lt;X, Y&gt; p(&amp;z); X *x = p; Y *y = p; return 0; } </code></pre> <p>If you're worried about the double storage of pointers, this approach doesn't work. See comments below this answer as to why incorporating Paweł's suggestion of using a union, which works if and only if all the pointers are numerically identical (that is, there's no multiple inheritance or other shenanigans using adjusted this pointers going on), is unsafe and basically useless.</p> <pre><code>// DON'T USE THIS VARIANT!!!! template &lt;typename... Ts&gt; class MultiPointer { public: MultiPointer(void *) {} }; template &lt;typename T, typename... Rest&gt; class MultiPointer&lt;T, Rest...&gt; { public: template &lt;typename U&gt; MultiPointer(U *u) : rest_(u) { ptr_ = u; }; template &lt;typename U&gt; operator U*() const { return rest_; } operator T*() const { return ptr_; } private: union { T *ptr_; MultiPointer&lt;Rest...&gt; rest_; }; }; </code></pre>
    singulars
    1. This table or related slice is empty.
    1. PO"dual inheritance" pointer
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USaddaon
    1. USaddaon
    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
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COIn the "single pointer storage" part of your answer: "if and only if all the pointers are numerically identical" I only see one possibility for a type `T` to have its super class pointers `A*` and `B*` pointing to the same address: if either `A` or `B` derives from the other and `T` derives from `A` or `B`, respectively. And it's clearly about multiple inheritance, where we don't want such a situation in most cases.
      singulars
      1. PO
      1. USleemes
    2. COleemes, it's implementation dependent, but in many implementations the pointers will be numerically identical in the absence of vtables (that is, the absence of virtual functions).
      singulars
      1. PO
      1. USaddaon
    3. COSo they store their content at the same place, i.e. overlapping? That would be a cool compression. Seriously, how is that possible? `class A { int x; }; class B { float y; }; class C : A, B {};` Now, `x` and `y` would share the same memory if `(void*)(A*)c == (void*)(B*)c`
      singulars
      1. PO
      1. USleemes
 

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