Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Why does fopen return NULL?
#include<stdio.h>
#include<stdlib.h>
int main (void){
FILE *cfPtr;
char name[15];
int ID;
if ((cfPtr = fopen("draft.txt","w")) == NULL){
printf("File could not be opened...\n"); //program gives me this as an output
}
}
Output:
File could not be opened...
2 answers
You are accessing this answer with a direct link, so it's being shown above all other answers regardless of its score. You can return to the normal view.
-
The simple explanation would be that you simply don't have write access to the path, which is one possibility.
-
Another weird phenomenon that may happen is that you are running a very old C compiler and it can't find
fopen- because you did forget to#include <stdio.h>.When this happens on modern compilers, you get a compiler error. On very old compilers (the "ANSI/C90 standard") the compiler would instead cook up some dumb initiative of its own and treat the function as if it returns
int. This could create very strange and subtle bugs.You could avoid such bugs by updating to the latest version of your C compiler. In case of gcc, clang or icc compilers you should also follow this advise: What compiler options are recommended for beginners learning C?
Unrelated to your question fflush(stdin); is undefined behavior and rarely the correct solution. Instead you should just ensure to consume the line feed character after taking the input. (For example by a getchar() call or by adding a space at the beginning of the scanf format string - but this is a topic for another thread.)
Besides the possible issues that Lundin told you, there is also the possibility that the current directory of the program is not what you think it is (note that the current directory is not necessarily the directory the executable is in, nor is it necessarily your user directory). This problem is unlikely if you started it directly from the command line, but if you started it through another program (for example from a file manager, or from your development environment), you might want to check that program's documentation on what directory it puts as current when it starts programs.
If the program is started from a directory you don't have a write permissions to, and the file does not yet exist there (which is likely if you are in the “wrong” directory), then the code will try to create it, which fails if you don't have write permission on the directory.
0 comment threads
1 comment thread