Thread: Invalid storage class for function

On which line does your compiler report that error and what is the exact error message?

My guess would be that the problem has something to do with you forward declaring getAndPrint to be static, but as I don't normally forward declare my static functions, I don't dare to say that that is the problem without some investigation of my own.

> fgets (data1 -2, sizeof(data1), search);
What are you hoping to achieve with this out of bound pointer to your buffer?

Do you just need to include the word "static" in front of your function definition (and not just in the prototype)?

Other problems:

Since dest is defined like this:
char dest[] = "/home/user/Desktop/folder/";
it does not have the storage to concatenate more chars into:
strcat (dest, mainFile);
Try this instead:
char dest[100] = "/home/user/Desktop/folder/";
and use strncat to prevent possible buffer overflow
strncat (dest, mainFile, sizeof dest - strlen(dest) - 1);

And in your fgets, why are you subtracting 2 from data1 and data2? That's undefined.

Also, you seem to be confused between the search and data FILE pointers.

Originally Posted by InicDominus

From the example code, it would be on line 3 after I have made the prototype. The error is "invalid storage class for function 'getAndPrint' ". If I dont declare the protoype static I get errors: "colficting types for 'getAndPrint", "previous implicit declaration of 'getAndPrint' was here", "static declaration of 'getAndPrint' follows non-static declaratation".

It might be good for you to reduce your program to the smallest and simplest program that you expect to compile but which demonstrates this problem, and post it. As it stands, it is possible to take your example code, fix an unrelated syntax error, then have a compilable (though incorrect) program.

Originally Posted by InicDominus

I know it may be sloppy as I have never used C before but it works fine.

It may appear to work fine, yet still be horribly wrong. One of the effects of undefined behaviour is that the code works perfectly until the moment that you really need it to work perfectly (e.g., when your program is being graded or when it is being demonstrated to the client).

> I know it may be sloppy as I have never used C before but it works fine.
So said the blind man who ran across the road, and survived the first time he tried it.

Yes, it is sloppy, and you'll get your ass handed to you on a plate at some point in the form of a segfault.
Feel free to carry on as you are, until I tell you to add
#include <I_told_you_so.h>

Never make the mistake of assuming "works" == "bug free" when it comes to C programming. All sorts of crap can seem to "work" in the beginning, only to crash and burn later on.