Another c struct syntax question

[Yusuf]

I'm sorry for the second post in as many hours, and both about structs.

The code below compiles. The variables test1 and test2 are structures
of datatype teststruct1 and teststruct2. The size of testintArray is
explictly set to 2 and 3 in teststruct1 and teststruct2. I want to
define a generic structure so that testintArray points to an array of
ints. The generic structure I have written is teststruct3.

What I can't seem to figure out is the syntax how to initialise test3
with data like I have done for test2 or test1 with syntax {1,{1,2,3}}.
I have had to do it a long way with malloc etc in function main. Can I
initialise the test3 instance of the struct teststring3 using a syntax
like{1,{1,2,3}} ?

I would appreciate help with the syntax. Thank you.
Yusuf
#include <stdlib.h>

struct teststruct1
{
int testint;
int testintArray[2];
} test1[3] =
{
{1,{1,2}},
{2,{1,9}},
{3,{2,9}}
};

struct teststruct2
{
int testint;
int testintArray[3];
} test2[3] =
{
{1,{1,2,3}},
{2,{1,4,5}},
{3,{2,3,1}}
};

//I want to initialise test3 like I have
//done with test2 and test1 above using the
//easy to read {1,{1,2,3}} syntax or something
//like it.
struct teststruct3
{
int testint;
int *testintArray;
} test3[3];

int main(void)
{
test3[0].testint=1;
int *testArray=mall oc(5*sizeof(int ));
testArray[0]=1;
testArray[1]=2;
testArray[2]=4;
testArray[3]=7;
testArray[4]=7;
test3[0].testintArray=t estArray;
return 0;
}

[Yusuf]

Thank you again Harald. This works too! I have really got to sit down
and study this code now and convince myself I really do understand it.
Regards
Yusuf

[Keith Thompson]

"kondal" <ko******@gmail .comwrites:
[...]

If you are using another array to initialize your structures, why don't
you use memcpy.

Create a integer pointer to the structure and memcpy the entire
structure. If not you can use it to initialize individually.

What do you mean by "integer pointer"? Do you mean just "pointer"?

It's not necessary to use memcpy() to copy structures; you can just
use an assignment.

--
Keith Thompson (The_Other_Keit h) ks***@mib.org <http://www.ghoti.net/~kst>
San Diego Supercomputer Center <* <http://users.sdsc.edu/~kst>
We must do something. This is something. Therefore, we must do this.

[Keith Thompson]

"Yusuf" <as**********@h otmail.comwrite s:
[...]

t2.c:26: warning: initialization from incompatible pointer type
Code below.
Thank you again
Yusaf
typedef struct
{
int testint;
int *testintArray;
} teststruct3;

struct teststruct4a
{
char *testchar;
struct teststruct3 *teststruct;
};

struct teststruct4b
{
char *testchar;
struct teststruct3 *teststruct;
} test4b[1] =
{
{"testchar",(te ststruct3[])
{
{1, (int []) { 1, 2, 3 } },
{2, (int []) { 3, 4, 5 } },
{3, (int []) { 6, 7, 8 } }
}
}
};

int main(void)
{
return 0;
}

For the sake of consistency, don't use typedefs. You originally
declared your "teststruct 3" type as "struct teststruct3 { ... };";
there was no reason to change that to a typedef. The problem was
that, later on, you referred to the type as "teststruct 3". You just
need to refer to it as "struct teststruct3".

A typedef for a struct type merely declares another name for something
that already has one. Some people like being able to refer to the
type with a single identifier, but it's not at all necessary.

(If you're going to use typedefs, you should be consistent; having
"teststruct 3" as a typedef name and "teststruct 4b" as a struct tag is
just confusing.)

--
Keith Thompson (The_Other_Keit h) ks***@mib.org <http://www.ghoti.net/~kst>
San Diego Supercomputer Center <* <http://users.sdsc.edu/~kst>
We must do something. This is something. Therefore, we must do this.