Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>In the example code, the destructor for <code>mystruct</code> is called at the end of <code>main</code>.</p> <p><strong>Pointers</strong> When a pointer falls out of scope, nothing happens to the object being pointed to. The lifetime of the object stays whatever it would have been had the pointer never existed. There is, of course, an important detail: objects created by <code>new</code>/<code>new[]</code> exist until they are <code>delete</code>d/<code>delete[]</code>d, and memory allocated by <code>malloc</code> exists until it's <code>free</code>d.</p> <p><strong>References</strong> A reference is nothing more than an additional name for an existing object. With the exceptions of a <code>const</code> reference pointing at a temporary object, the reference's lifetime has no effect on the object-being-referred-to's-lifetime; the destructor is called when that object falls out of scope normally (a <code>const</code> reference to a temporary object keeps the temporary alive until the <code>const</code> reference falls out of scope).</p> <p><a href="https://stackoverflow.com/a/4715888/103167">Using the term "object" is a simplification</a>, the pointer or reference really points at memory; it doesn't "track" the actual object in any way. For instance, it is possible to destroy an object being pointed to before the pointer falls out of scope, or to destroy an object being referenced before the reference falls out of scope. These invalid pointers/references are called "dangling pointers" and "dangling references" respectively:</p> <pre><code>int* i = new int(5); int&amp; j = *i; delete i; // i is now a dangling pointer, and j is now a dangling reference </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POScope of an object when passed by references versus passed by pointers
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USMax Lybbert
    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
    1. COA reference is actually a name for a memory location, not the object. I explained that more thoroughly [here](http://stackoverflow.com/a/4715888/103167).
      singulars
      1. PO
      1. USBen Voigt
    2. CO@BenVoigt Thanks. I've added a paragraph with that link. And, I'll admit that I hadn't thought of ways to create dangling references.
      singulars
      1. PO
      1. USMax Lybbert
    3. COI'm not even talking about dangling references. It's legal to create a new object in the same memory as the old one, and as long as the type match, existing references work correctly with the new object.
      singulars
      1. PO
      1. USBen Voigt
 

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