Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!pilchuck!dataio!bright
From: bright@Data-IO.COM (Walter Bright)
Newsgroups: comp.lang.c
Subject: Re: Nested Comments in C -- A recent experience
Message-ID: <2387@dataio.Data-IO.COM>
Date: 19 Mar 90 20:36:12 GMT
References: <2381@dataio.Data-IO.COM> <12351@goofy.megatest.UUCP>
Reply-To: bright@Data-IO.COM (Walter Bright)
Organization: Data I/O Corporation; Redmond, WA
Lines: 10

In article <12351@goofy.megatest.UUCP> djones@megatest.UUCP (Dave Jones) writes:
<From article <2381@dataio.Data-IO.COM>, by bright@Data-IO.COM (Walter Bright):
<< <    (void) memcpy((void *) &x, (void *) &y, sizeof(y));
<< It's more readable if you eliminate the redundant clutter:
<< 	memcpy(&x,&y,sizeof(y));	/* Copy y into x	*/
<Strictly speaking, you have to keep the (void*) casts, just in case some
<enemy system codes some kinds of pointers in screwy ways. It can happen.

Not so. If memcpy is prototyped properly, the (void*) casts will be
inserted automagically by the compiler.