Re: "PORTING C" > NULL problem!
- From: "Igor Tandetnik" <itandetnik@xxxxxxxx>
- Date: Tue, 9 Feb 2010 07:36:45 -0500
Ulrich Eckhardt wrote:
A void pointer doesn't have any type
This is not true formally, and I don't think it's useful to think this way informally either:
6.2.5p19 The void type comprises an empty set of values; it is an incomplete type that cannot be completed.
The type of a void pointer is, of course, void*.
--
With best wishes,
Igor Tandetnik
With sufficient thrust, pigs fly just fine. However, this is not necessarily a good idea. It is hard to be sure where they are going to land, and it could be dangerous sitting under them as they fly overhead. -- RFC 1925
.
- Follow-Ups:
- Re: "PORTING C" > NULL problem!
- From: Ulrich Eckhardt
- Re: "PORTING C" > NULL problem!
- References:
- "PORTING C" > NULL problem!
- From: Robby
- Re: "PORTING C" > NULL problem!
- From: Igor Tandetnik
- Re: "PORTING C" > NULL problem!
- From: Robby
- Re: "PORTING C" > NULL problem!
- From: Ulrich Eckhardt
- "PORTING C" > NULL problem!
- Prev by Date: Re: Using TCHAR with pcap and sockets (send/recv/setsockopt)
- Next by Date: Re: "PORTING C" > NULL problem!
- Previous by thread: Re: "PORTING C" > NULL problem!
- Next by thread: Re: "PORTING C" > NULL problem!
- Index(es):
Relevant Pages
|