Re: Avoiding dangling pointers.

Rafael Anschau wrote:
> I read that you should assign null (0) to all pointers that you call
> delete on.
> 
> Does that mean:
> 
> *p=0(set the value pointed to to 0).
> 
> or
> 
> p=0(set the address held to zero).
> 
<snip>

Can I make a please for something that Micro$oft might have got right?

In debug mode, they zap the contents of any deleted memory with the
pattern 0xDDDDDDDD.  This is invalid as an address on their usual
architecture (i.e. Win32), and tends to get spotted quickly.

If you do this with your pointers as you delete them - but only when in
debug mode, else it's a waste of CPU - you'll pick up double deletes as
well as accessed to deleted memory.

You'll have to pick your own value to scribble on the data - a good one
is implementation dependent.

Of course, this code belongs in your smart pointer class...

Andy

-- 
      [ See http://www.gotw.ca/resources/clcm.htm
for info about ]
      [ comp.lang.c++.moderated.    First time posters: Do this! ]