Where are files created during File handling using Dev C++ compiler??

[Dushyant]

Hi,

Can anyone tell me the folder where the files created during file handling program are stored?? I am using Dev C++ IDE......

For ex- fpointer = fopen("library.bin","w");

Where does library.bin gets created? What folder?

[WaltP]

Most likely in the folder with the .EXE file -- where the program itself resides.

[grumpy]

This is not actually a C question. It depends on a few things, unrelated to C. It is generally placed in the current working directory, which is set when the program is run.

IDE's are actually able to specify the working directory that they start programs in - the way to make that setting depends on IDE. If that setting is not specified, the directory is usually the directory containing your executable. In some cases, it is the directory containing the executable for the IDE itself.

Bear in mind that some programs can set their own working directory - under posix, for example, by using a function called chdir().

Some operating systems provide means of controlling the working directory when starting a program. For example, it is common for shorttcuts under windows to specify the working directory for a program they link to.

[rags_to_riches]

You know what else works here?

1. Compile the program.
2. Run the program.
3. Use the search functionality of your OS to search for the created file.

This is logical. Logic is required to be a programmer. I don't know how any programmer could not figure this out on his or her own.

[WaltP]

Are you saying that once you install a compiler you are a programmer?
Or once you write you first program you are a programmer?

I disagree.

IMO, you become a programmer more when you are able to figure it out, therefore, he's not a programmer yet.

[stahta01]

Are you saying that once you install a compiler you are a programmer?
Or once you write you first program you are a programmer?

I disagree.

IMO, you become a programmer more when you are able to figure it out, therefore, he's not a programmer yet.

I say once you write, compile, and run the first program that works right you are at least a bad programmer.
I do consider the requirements to be a good programmer much higher.

Tim S.

[grumpy]

I say once you write, compile, and run the first program that works right you are at least a bad programmer.
I do consider the requirements to be a good programmer much higher.

Given the rate of flaws that occur even in well-engineered programs (1-5 errors per thousand lines of code) it might be argued that nobody can be a good programmer unless the bar to being "good" is set pretty damned low.

[Dushyant]

I am just a learner.....
Or may be an awsome programmer in near future...

Thanx to all of you anyway.....