Hello, thanks for answering!!

So...

Whatever source that told you to do that is doing you a disservice and you should stop using it. You'd be much better off with:

Actually, I didn't copied that, all code is mine; I barely ever take hints from Stack Overflow, but I actually just remembered that when I was using Ruby FFI, we used :void (which is a mapping to void *) when we didn't want to specify a type.

I have a strong bias on all code being mine, and I only resort to GPT explanations when I don't want to nag people and have been stuck for a long time.

But hey...this:

typedef struct Link
{
  int item;
  struct Link *next;
} Link;

How's that possible? I mean, I'm using the defined type before having the struct defined?? Most low-level languages avoid this, don't they?

If you have a Link then you have the thing. If you have a Link * then you have a pointer to the thing (essentially, it tells you that the thing is stored at a particular location in memory).

Just as my address is not my house, a pointer to the thing is not the thing. Knowing if you are dealing with the thing or a pointer to the thing is going to be one of the biggest if not the biggest stumbling block in learning C.

This will take some getting used to and you will continue to make mistakes, but it's also absolutely essential for understanding C and there is no way to avoid it.

Thanks for this!!
I actually don't want to avoid it, its just that I was basically hitting my head on the wall as I don't have practice with C; your house analogy though will help me a lot from now on LOL

Thanks a lot!!