Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You can use a technique presented by <a href="http://www.boost.org/doc/libs/1_43_0/libs/smart_ptr/sp_techniques.html#preventing_delete" rel="nofollow noreferrer">Boost</a>, but my concern is that you're allowing implicit conversions from a smart pointer to a raw pointer, which is generally frowned upon on. Besides, users can call <code>delete</code> on a pointer obtained by the <code>-&gt;</code> operator, so there's really nothing you can do to prevent a determined idiot to work around whatever mechanism you come up with.</p> <p>You really should just implement a <code>get()</code> method instead of providing <code>operator T*()</code> so that at least calls to <code>delete smartptr</code> will not compile. Non-idiots should be able to figure out that there's probably a reason why that won't work.</p> <p>Yes, it's more work to type out <code>LegacyFunc(smartptr.get())</code> than <code>LegacyFunc(smartptr)</code>, but the former is preferred since it makes it explicit and prevents unexpected conversions from happening, like <code>delete smartptr</code>.</p> <p>What if you have functions like this:</p> <pre><code> void LegacyOwnPointer(SomeType* ptr); </code></pre> <p>where the function will store the pointer somewhere? This will screw up the smart pointer, because now it's not aware that something else is owning the raw pointer.</p> <p>Either way, you have some work to do. Smart pointers are like raw pointers, but they are not the same, so you can't just find-and-replace all instances of <code>T*</code> and replace it with <code>my_scoped_ptr&lt;T&gt;</code> and expect it to work just as well as before.</p>
    singulars
    1. This table or related slice is empty.
    1. POC++ "smart pointer" template that auto-converts to bare pointer but can't be explicitly deleted
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USIn silico
    1. USIn silico
    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. COThat's a different problem.
      singulars
      1. PO
      1. USGManNickG
    2. COWhether or not it is frowned upon, it would be hopeless to try to shoehorn smart pointers into this legacy code base without an implicit conversion to the raw pointer. There's just too many places where you need to provide the raw pointer. -- Your suggestion only helps if I can modify the pointed-to class, which I can't, in general. I need a technique that works entirely within the smart pointer class.
      singulars
      1. PO
      1. USzwol
    3. COI really don't think you appreciate the realities of working in a 3-million-line, 15-year-old code base. If I took the implicit conversion out of the smart pointer template (which is already heavily used), I would have to put in *thousands* of .get() calls and my coworkers would lynch me.
      singulars
      1. PO
      1. USzwol
 

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