Re: Returning automatic pointers always bad?
- From: Richard Heathfield <rjh@xxxxxxxxxxxxxxx>
- Date: Sat, 28 Feb 2009 11:38:57 +0000
pete said:
Richard wrote:<snip>
His reasoning was correct enough if you dig into what he said :
"the pointer is assigned to another pointer which then continues
to point to valid memory". Implicit is "pointer value" when
mentioning assigning a "pointer" in this kind of chat.
No.
He's a troll. What did you expect from a troll - an accurate
response?
Please consider doing us all a favour, pete.
--
Richard Heathfield <http://www.cpax.org.uk>
Email: -http://www. +rjh@
Google users: <http://www.cpax.org.uk/prg/writings/googly.php>
"Usenet is a strange place" - dmr 29 July 1999
.
- References:
- Returning automatic pointers always bad?
- From: C . J . Clegg
- Re: Returning automatic pointers always bad?
- From: pete
- Re: Returning automatic pointers always bad?
- From: Richard
- Re: Returning automatic pointers always bad?
- From: pete
- Returning automatic pointers always bad?
- Prev by Date: Re: usage of fwide function
- Next by Date: Re: Returning automatic pointers always bad?
- Previous by thread: Re: Returning automatic pointers always bad?
- Next by thread: Re: Returning automatic pointers always bad?
- Index(es):
Relevant Pages
|