Thread: Allocating functions to an array of function pointers inside a struct

Originally Posted by tabstop

I think you may be mistaken on what a struct is. A struct is not a thing. A struct is what a thing would look like, if it were to exist. You have to create an object to actually have something. So:

Code:

struct hey_a_struct {
    int numbers[10];
}

/* at this point I have nothing at all */
int main(void) {
struct hey_a_struct object; /*now I have something */
for (int i = 0; i < 10; i++) {
    object.numbers[i] = i*i;
}

Completely wrong. The first definition of the struct does indeed reserve the memory for it. It is usable.
struct hey_a_struct object; will define a second struct with the same shape.

The HP store called, those first two letters in your name need to be returned.

Sorry. My mistake. Who would do such a thing as "define" a struct in this way. (I'm used to putting its name at the end in which case it would make sense.)
Or else use typedef. I get confused whether the name is just after 'struct', or at the end, vs. when using typedef.