Apologies if this is covered by "standard" (ANSI) C practices, but I could not find it
but what's the rational behind having a .h and .c file for #includes,
Currently I create my defines and prototypes at the top of my .c file and do not use .h files. then I just use #include
Is there a reason for splitting the two - seems like it makes for more hassles in file management.
PS Thanks for all the help you constantly provide this forum[/b]