Re: TCP connect in Non Blocking Mode
- From: Alex Fraser <me@xxxxxxxxxxx>
- Date: Mon, 28 Apr 2008 23:12:07 +0100
Rainer Weikusat wrote:
[snip]
It specifies the case I was refering to, which happened to be the one
the discussion had moved to at this point [...]
OK, so you were responding only to the suggestion of also checking for readability, ignoring the reason for that suggestion, right? The context seemed (and still seems) important to me, so ignoring it came across like you hadn't read it.
Put another way, there is a difference between "set the pointer to NULL after calling free()" and "set pointers to NULL after calling free()" - you seem to be responding to the former as if it were the latter.
Alex
.
- Follow-Ups:
- Re: TCP connect in Non Blocking Mode
- From: Rainer Weikusat
- Re: TCP connect in Non Blocking Mode
- From: David Schwartz
- Re: TCP connect in Non Blocking Mode
- References:
- TCP connect in Non Blocking Mode
- From: Prabhu
- Re: TCP connect in Non Blocking Mode
- From: Rainer Temme
- Re: TCP connect in Non Blocking Mode
- From: David Schwartz
- Re: TCP connect in Non Blocking Mode
- From: Rainer Temme
- Re: TCP connect in Non Blocking Mode
- From: David Schwartz
- Re: TCP connect in Non Blocking Mode
- From: Rainer Temme
- Re: TCP connect in Non Blocking Mode
- From: Rainer Weikusat
- Re: TCP connect in Non Blocking Mode
- From: Alex Fraser
- Re: TCP connect in Non Blocking Mode
- From: Rainer Weikusat
- TCP connect in Non Blocking Mode
- Prev by Date: Re: Timer in C
- Next by Date: Re: sharing memory map between processes (same parent)
- Previous by thread: Re: TCP connect in Non Blocking Mode
- Next by thread: Re: TCP connect in Non Blocking Mode
- Index(es):
Relevant Pages
|