🚀 go-pugleaf

In article <1992Oct16.094939.11437@waikato.ac.nz> banksie@khantazi.welly.gen.nz writes:
>Philip R. Banks writes:
>>    Okay here is a little wee problem I am hoping some C type can answer for
>> me. Quickly please, before I take to this compiler with a blunt
>> instrument... :)
>> 
>> The problems is thus I have defined a structure like so :-
>> 
>> typedef struct {
>>    char *name;
>>    char *comment;
>>    struct filenode *next;
>>    struct filenode *prev;
>>    struct filenode *parent;
>>    struct filenode *sublist;
>>    int load;
>>    int exec;
>>    int length;
>>    char flag;
>> } filenode;
>
>Hmm.  Well, I can see problems already!  The type name 'filenode' isn't defined
>within the structure definition!  It's not defined until the end of the typedef
>has been reached.

	Well he isn't referencing "type name filenode" from within the
	structure definition.  The compiler will not complain at this
	stage because it knows how big the pointer to structure is, which
	is the same as pointer to anything, i.e. 1 word.  Philip is getting
	confused between structs and typedef names and this can be made
	more obvious by doing:
	
		struct filenode {
		
			blah... blah... blah
		
		};
		
		typedef struct filenode *FileNode;
	

-- 
Andy Duplain, BT Customer Systems, Brighton, UK.            duplain@rtf.bt.co.uk
#define	DISCLAIMER      My views and opinions are my own, and not my company's