Smart pointers impractical a lot of the time
Chandra Shekhar Kumar <firstname.lastname@example.org> wrote in message news:<3EF64860.3FCC6E7F@oracle.com>...
> donot use dude pointers ...use smart pointer instead
There's a problem with this approach. You have three options for using
1) Use the standard library's auto_ptr,
2) Use one from another library, or
3) Write your own.
Option 3 is out because it requires intimate knowledge of the
different ways smart pointers can work and the uses it will be
subjected to. The poster is asking what the point of pointers is
(haha... *sees pun*) so I think it's safe to assume that neither of
these points are met.
Option 2 is better, but the lack of any standard implementation of
smart pointers (besides auto_ptr) means that generic books can't teach
it, libraries can't make good use of it, etc. Probably because of this
(and in spite of auto_ptr) I didn't know what smart pointers were
until a few days ago despite C++ programming for a couple years.
Option 1 is the most promising until you realize that the auto_ptr
doesn't behave appropriately in most circumstances. If the stardard
library had a painter with reference counting, then things wauld be in
much better shape.
Re: Smart pointers impractical a lot of the time
In article <email@example.com >, Evan
| 1) Use the standard library's auto_ptr,
| Option 1 is the most promising until you realize that the auto_ptr
| doesn't behave appropriately in most circumstances. If the stardard
| library had a painter with reference counting, then things wauld be in
| much better shape.
We're getting there...
This was voted into a "Library Technical Report" just this Spring.
Vendors may ship it in namespace std::tr1 in the near future.
|All times are GMT. The time now is 12:13 PM.|
Powered by vBulletin®. Copyright ©2000 - 2014, vBulletin Solutions, Inc.
SEO by vBSEO ©2010, Crawlability, Inc.