fopen() with full path affecting subsequent fopen calls

**vippstar@gmail.com** · Jun 27 '08, 07:33 PM

Re: fopen() with full path affecting subsequent fopen calls

On Apr 28, 3:14 pm, Michel Rouzic <Michel0...@yah oo.frwrote:

I made a program that accepts as parameters an input file name that
we'll call file1, and an output file name that we'll call file2, and
opens on its own a configuration file called file3. My program works
correctly when calling it like this : ./program file1 file2, and also
with full paths, like this : ./program c:\dir\file1 c:\dir\file2
>
However, a most puzzling phenomenon occurs when I use the full path
only for the first file, like this : ./program c:\dir\file1 file2.
Normally I would expect file2 to be written in the same place as it
did when I didn't use the full path for file1. Only that's not what
happens. File2 gets successfully written to, as well as file3 (which
my program loads data from and saves data into), only not where I
expect, and actually, I don't have a single clue where they can be.
They're surely getting written to a valid place because the program
operates normally and file3, the one from the mysterious location,
gets read from normally.
>
So here's my problem stated in a more concise manner : if I call
fopen() using a full path, it affects subsequent fopen() calls in that
if they don't call absolute paths they will try to reach the files in
an unknown location, which is definitely not what I want.

Of course it does not. We can't be 100% sure of what actually happends
without seeing your code.
Try to isolate the problem in the least lines possible before you post
it.

**Bill Reid** · Jun 27 '08, 07:33 PM

Re: fopen() with full path affecting subsequent fopen calls

<vippstar@gmail .comwrote in message
news:62863177-18a1-4d95-b60a-fe10d3c142f9@j2 2g2000hsf.googl egroups.com...

On Apr 28, 3:14 pm, Michel Rouzic <Michel0...@yah oo.frwrote:

I made a program that accepts as parameters an input file name that
we'll call file1, and an output file name that we'll call file2, and
opens on its own a configuration file called file3. My program works
correctly when calling it like this : ./program file1 file2, and also
with full paths, like this : ./program c:\dir\file1 c:\dir\file2

However, a most puzzling phenomenon occurs when I use the full path
only for the first file, like this : ./program c:\dir\file1 file2.
Normally I would expect file2 to be written in the same place as it
did when I didn't use the full path for file1. Only that's not what
happens. File2 gets successfully written to, as well as file3 (which
my program loads data from and saves data into), only not where I
expect, and actually, I don't have a single clue where they can be.
They're surely getting written to a valid place because the program
operates normally and file3, the one from the mysterious location,
gets read from normally.

So here's my problem stated in a more concise manner : if I call
fopen() using a full path, it affects subsequent fopen() calls in that
if they don't call absolute paths they will try to reach the files in
an unknown location, which is definitely not what I want.

Of course it does not. We can't be 100% sure of what actually happends
without seeing your code.
Try to isolate the problem in the least lines possible before you post
it.

It's very likely a "current working directory" problem of some sort,
and of course, not a part of the "C" standard, like all directory issues.
Despite the egregious off-topic nature of the post, he should search
through the documentation for his compiler for functions that change
the "current working directory", and then evaluate carefully what
that directory would be at each fopen() call.

---
William Ernest Reid

**Richard Tobin** · Jun 27 '08, 07:33 PM

Re: fopen() with full path affecting subsequent fopen calls

In article <dHkRj.135868$D _3.120626@bgtns c05-news.ops.worldn et.att.net>,
Bill Reid <hormelfree@hap pyhealthy.netwr ote:

>It's very likely a "current working directory" problem of some sort,
>and of course, not a part of the "C" standard, like all directory issues.
>Despite the egregious off-topic nature of the post, he should search
>through the documentation for his compiler for functions that change
>the "current working directory", and then evaluate carefully what
>that directory would be at each fopen() call.

It might be useful to print out the current directory before each call
to fopen(), to see if it's changing. I take it from the filenames
that it's a Windows system, but quite likely the Posix getcwd()
function will be available.

-- Richard
--
:wq

**Michel Rouzic** · Jun 27 '08, 07:33 PM

Re: fopen() with full path affecting subsequent fopen calls

Bill Reid wrote:

It's very likely a "current working directory" problem of some sort,
and of course, not a part of the "C" standard, like all directory issues.
Despite the egregious off-topic nature of the post, he should search
through the documentation for his compiler for functions that change
the "current working directory", and then evaluate carefully what
that directory would be at each fopen() call.

My bad, seems like I mis-reported my problem. It seems to only happen
when I drag and drop file1 on the program. I used your advice and did
a getcwd() and as it turns out when and only when I drag and drop
file1 on the program, the current working directory changes to c:
\windows\system 32, and that happens even before any fopen() call.

My apologies, this is decidedly a platform specific problem.

fopen() with full path affecting subsequent fopen calls

fopen() with full path affecting subsequent fopen calls

Comment

Comment

Comment

Comment