it always says p undefined, even though it works on my friends computer.Code:#include <stdio.h> #include <stdlib.h> FILE * p; int main() { p=fopen("meryem.txt","a+"); if(fopen("meryem.txt","a+")) { printf("dosya acıldı:"); } else printf("dosya acılamadı:"); fclose(p); }
p *is* defined, so either your headers are missing or broken (i.e compiler /IDE configuration issues). My compiler doesn't complain about that code at all (though it does complain about you not returning anything from main - stick a return(EXIT_SUCCESS) in at the end of that function).
P.S. Your text is in UTF-8, so I assume you have a UTF-8 compatible compiler?
P.P.S. Learn to indent properly.
- Compiler warnings are like "Bridge Out Ahead" warnings. DON'T just ignore them.
- A compiler error is something SO stupid that the compiler genuinely can't carry on with its job. A compiler warning is the compiler saying "Well, that's bloody stupid but if you WANT to ignore me..." and carrying on.
- The best debugging tool in the world is a bunch of printf()'s for everything important around the bits you think might be wrong.
i dont have a problem with anything else, i use codeblocks and even though it works on my friends computer it doesnt always work on mine. i dont think the headers are missing or broken..
You should copy/paste your compiler error.
there is some problem with your codeblocks settings not the code
Put it this way - a million people would have jumped on your code by now if there was a problem with it (and even I mentioned two completely unrelated things about it). The code is fine. If a FILE isn't defined properly, that's because you didn't #include stdio.h (which you have) or because the compiler can't *find* stdio.h. FILE is pretty much an in-built feature of the C standard library and not likely to be missing from your compiler entirely. You're not looking at something that's staring you in the face - your development environment is bugged. Either you're not heeding warnings/errors that it's throwing at you, or it's not doing what you think it's doing.Originally Posted by zeybek258388
That code compiles perfectly. FILE is well-defined in all C environments so long as you #include stdio.h (which you have). The problem's not the code.
- Compiler warnings are like "Bridge Out Ahead" warnings. DON'T just ignore them.
- A compiler error is something SO stupid that the compiler genuinely can't carry on with its job. A compiler warning is the compiler saying "Well, that's bloody stupid but if you WANT to ignore me..." and carrying on.
- The best debugging tool in the world is a bunch of printf()'s for everything important around the bits you think might be wrong.
FAQ-Compiling (errors) - CodeBlocks
Tim S.
"...a computer is a stupid machine with the ability to do incredibly smart things, while computer programmers are smart people with the ability to do incredibly stupid things. They are,in short, a perfect match.." Bill Bryson
