What textbook C++ knowledge is an anti-pattern now?
<p>I'm looking for X-Y pairs, where X is possibly described in stock C++ textbooks but became a little bit obsolete or turned out to be counterproductive, while Y is the advised alternative.</p>

<p>If you feel that X is really obsolete but has no alternative, that may be ok to. Also, if you think Y is really useful and common nowadays but doesn't have a related X, I'm interested in that too.</p>

<p>For example (sources uncited, might not be actually correct, feel free to post these if you feel like):</p>

<ul>
<li>Old: everyday use of raw pointers (<code>*</code>). New: <code>scoped_ptr</code>, <code>auto_ptr</code> or <code>shared_ptr</code></li>
<li>Old: deep subclass hierarchies. New: rather delegate</li>
<li>Old: <code>std</code> is fun. New: <code>std</code> can bite you at corner cases, rather use some <code>boost</code> stuff</li>
<li>Old: rigidly avoiding virtual methods because they might be slow (or)</li>
<li>New: RAII</li>
<li>...</li>
</ul>

<p>Please add a <em>single entry per post</em>, possibly with a short explanation or a reference to an external description or SO post.</p>
