I am trying to read an input file, but so far I've had to have the file in the same folder as the workspace for it to be found. I open it as follows:
I've tried entering a path for the file, ie.Code:inp = fopen("test_outp.bin", "rb");
But an error message comes up that the file is not found.Code:inp = fopen("c:\test\test_outp.bin", "rb");
I nkow other compilers can have a path specified for the input files, I can't figure it out with Visual C++.
Any idea?
backslashes need to be "escaped" so...
inp = fopen("c:\\test\\test_outp.bin", "rb");
"You are stupid! You are stupid! Oh, and don't forget, you are STUPID!" - Dexter
Or use forward slashes.Code:inp = fopen("c:/test/test_outp.bin", "rb");
Last edited by Dave_Sinkula; 05-25-2005 at 12:06 PM.
7. It is easier to write an incorrect program than understand a correct one.
40. There are two ways to write error-free programs; only the third one works.*
Thanks.
A.
It refuses to work if the user enters the file path, ie:
If the file provided is in the same directory as the project there is no error. Once you put in a file path, it errors out.Code:int main (void) { FILE *inp; char InFileName[100]; printf("Please enter the complete file path for the file to be parceled:\nEx.c:/Test/test_outp.baf\n"); scanf("%s", &InFileName); inp = fopen(InFileName, "rb"); if(!inp) printf("The file could not be opened.\n"); return 0; }
FAQ > How do I... (Level 1) > Get a line of text from the user/keyboard (C)Code:#include <stdio.h> #include <string.h> int main(void) { char filename[32]; FILE *file; fputs("filename? ", stdout); fflush(stdout); if ( fgets(filename, sizeof filename, stdin) ) { char *newline = strchr(filename, '\n'); if ( newline ) { *newline = '\0'; } } file = fopen(filename, "r"); if ( file ) { printf("opened \"%s\"\n", filename); fclose(file); } else { perror(filename); } return 0; } /* my output filename? c:/test/test.c opened "c:/test/test.c" */ /* my output filename? nothing nothing: No such file or directory */
Last edited by Dave_Sinkula; 05-25-2005 at 01:50 PM. Reason: Added second output.
7. It is easier to write an incorrect program than understand a correct one.
40. There are two ways to write error-free programs; only the third one works.*
