Re: AutoPtr::operator == : Is it defined the correct way ??
- From: "Gabest" <gabest@xxxxxxxxxxx>
- Date: Mon, 20 Mar 2006 13:28:08 +0100
Let's think further. If comparison is meaningless, why would anyone bother
using this operator? I'm using CAutoPtr quite frequently in a big project
but cannot remember ever needing it. On the other hand, I always think of
CAutoPtr variables as pointers, and this operator doing a value equality
check would bend my mind a bit. It could be that operator == was only
defined for completness. When I design a new class I also tend to add a few
common functions which are never going to be used.
.
- Follow-Ups:
- Re: AutoPtr::operator == : Is it defined the correct way ??
- From: P.GopalaKrishna
- Re: AutoPtr::operator == : Is it defined the correct way ??
- Prev by Date: Re: AutoPtr::operator == : Is it defined the correct way ??
- Next by Date: Re: virtual HRESULT STDMETHODCALLTYPE method (STDMETHOD)
- Previous by thread: Re: AutoPtr::operator == : Is it defined the correct way ??
- Next by thread: Re: AutoPtr::operator == : Is it defined the correct way ??
- Index(es):