Kenneth said:
Oh deary deary me. Here's some of the stuff from that page.
"Usually, the structure definition is saved as an #include member in a
maclib library,"
Er, no. Usually the structure definition is saved in a source file, the
details of which are entirely a matter between you and your system.
"but it can be placed at the top of the program."
Or, indeed, in other places.
"The commonest way to define structures is with a typedef, as shown below."
No. A typedef doesn't define anything.
"typedef struct country
{
char name[20];
int population;
char language[10];
} Country;
This defines a structure which can be referred to either as 'struct
country' or Country, whichever you prefer."
In a way, that's true. This bit: struct country { char name[20]; int
population; char language[10]; } defines a new type, and the rest creates a
synonym, 'Country', for that type.
"Strictly speaking, you don't need a tag name both before and after the
braces if you're not going to use one or the other."
But really strictly speaking, the name after the braces is not a tag name.
It's a type name.
"But it's standard practice to put them both in and to give them the same
name, but with the one after the braces starting with an uppercase letter."
No, that is not standard practice at all.
That slice of the page was sufficiently broken that I looked no further. I
cannot recommend that tutorial.
