Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

C: Assigning structures

Name: Anonymous 2010-07-24 2:09

suppose we have the following type:

typedef struct {
    int bar;
    int baz;
    int foo;
} Something;


In order to do a copy, I usually do something like:

Something a, b;
...
memcpy ((void *) &a, (const void *) &b, sizeof(Something));

But also the following is legal (and far more quick to write).

Something a, b;
...
a = b;

Is there any disadvantage in doing the second one?

Name: Anonymous 2010-07-26 9:12

>>17
To put what >>18 is saying more clearly, memcpy is part of the C standard library. The compiler ought to be able to optimize it just as well because its semantics are standardized. (A problem occurs, however, when you apply this logic to something like malloc.)

Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List