Re: void * in ANSC
- From: Harald van Dijk <truedfx@xxxxxxxxx>
- Date: Mon, 04 Feb 2008 23:25:07 +0100
On Mon, 04 Feb 2008 22:21:04 +0000, Walter Roberson wrote:
In article <fo6th2$mls$2@xxxxxxxxxxxx>, Army1987 <army1987@xxxxxxxxx>
wrote:
Army1987 wrote:
(void)memcpy(foo, bar, 42) accesses 42 bytes.
84 bytes, I meant.
How do you arrive at that number? memcpy() does not define the behaviour
if the fields overlap.
So assuming the fields don't overlap, memcpy reads 42 bytes, and writes
42 different bytes, so accesses 84 bytes in total.
.
- Follow-Ups:
- Re: void * in ANSC
- From: Walter Roberson
- Re: void * in ANSC
- References:
- void * in ANSC
- From: Mark Jiao
- Re: void * in ANSC
- From: Peter Nilsson
- Re: void * in ANSC
- From: Army1987
- Re: void * in ANSC
- From: Army1987
- Re: void * in ANSC
- From: Walter Roberson
- void * in ANSC
- Prev by Date: Re: void * in ANSC
- Next by Date: Re: xmalloc string functions
- Previous by thread: Re: void * in ANSC
- Next by thread: Re: void * in ANSC
- Index(es):