"amccombs" <amccombs@discussions.microsoft.com> ha scritto nel messaggio
news:1904E75B-987A-46C4-86E5-BF7770C5173C@microsoft.com...
char szBuffer[100];
typedef struct T_Smoo
{
struct
{
int a;
}H;
struct
{
int b;
int c;
int d;
}D;
} Smoo;
Your code seems to me C code (not C++), in fact you are using the syntax:
typedef struct ...
In C++, you can have just struct, without typedef.
I would suggest you to use C++ instead of C for application development.
You may also program "in C style", but if you use a .cpp extension for your
source codes, the C++ compiler (not the C compiler) will be used, and I do
think that you could have benefits, also using just "C++ as a better C".
For example, you can use "struct" without the more verbose "typedef".
However, I would write code a bit differently, e.g.
struct HBlock
{
int a;
};
struct DBlock
{
int b;
int c;
int d;
};
struct Smoo
{
HBlock H;
DBlock D;
};
Smoo *pSmoo = (Smoo*) szBuffer;
I fail to understand that... could you please clarify your goals?
Why are you type-casting from a char array to a Smoo custom class?
If you want to create a new Smoo instance, you may do:
Smoo * pSmoo = new Smoo();
You should release somewhere the object, using:
delete pSmoo;
pSmoo = NULL; // avoid dangling referneces
Frankly speaking, I would not use raw pointers, but I would prefer using a
smart pointer, like boost::shared_ptr (with it, basically, you don't need to
spend time thinking about delete).
pSmoo->H.a = 1;
pSmoo->D.b = 2;
pSmoo->D.c = 3;
pSmoo->D.d = 4;
OK
int offset = sizeof(pSmoo->H);
Smoo::D *p = (&Smoo::D) &szBuffer[offset];
If you want p to be a pointer to DBlock, and point to the "D" member in
Smoo, you may do like so:
DBlock * p = &(pSmoo->D);
p->D.b = 5;
p->D.c = 6;
p->D.d = 7;
No, it's: p->b = ...; p->c = ....; p->d = ...;
Giovanni
Smoo *pSmoo = (Smoo*) szBuffer;
why? because szBuffer will be sent through a socket connection. This is how