Directory path

[cjw]

Pl help me with this simple question.
I am using an array to store the file name,
eg. char in[] = "filename.bmp"; How can I give the directory path with
the file name?

[Arthur J. O'Dwyer]

On Wed, 8 Oct 2003, cjw wrote:

Pl help me with this simple question.
I am using an array to store the file name,
eg. char in[] = "filename.bmp"; How can I give the directory
path with the file name?

char in_plus_path[] = "c:\\mystuff\\filename.bmp";
char unix_style[] = "/mystuff/filename.bmp";

What are you really trying to do?

-Arthur

[Dan Pop]

In <Pi***********************************@unix46.andr ew.cmu.edu> "Arthur J. O'Dwyer" <aj*@nospam.andrew.cmu.edu> writes:

On Wed, 8 Oct 2003, cjw wrote:

Pl help me with this simple question.
I am using an array to store the file name,
eg. char in[] = "filename.bmp"; How can I give the directory
path with the file name?

char in_plus_path[] = "c:\\mystuff\\filename.bmp";

"c:/mystuff/filename.bmp" looks much better as a Windows path.

Many non-Unix implementations support Unix-style paths, even if the
native convention is different.

Dan
--
Dan Pop
DESY Zeuthen, RZ group
Email: Da*****@ifh.de

[Kris Wempa]

"Dan Pop" <Da*****@cern.ch> wrote in message
news:bm**********@sunnews.cern.ch...

In <Pi***********************************@unix46.andr ew.cmu.edu> "Arthur J. O'Dwyer" <aj*@nospam.andrew.cmu.edu> writes:

"c:/mystuff/filename.bmp" looks much better as a Windows path.

Many non-Unix implementations support Unix-style paths, even if the
native convention is different.

This works only on the NT/2000/XP versions of Windows. The 95/98/ME
versions do not accept the forward slashes.

[Dan Pop]

In <bm*********@kcweb01.netnews.att.com> "Kris Wempa" <calmincents(NO_SPAM)@yahoo.com> writes:

"Dan Pop" <Da*****@cern.ch> wrote in message
news:bm**********@sunnews.cern.ch...

In <Pi***********************************@unix46.andr ew.cmu.edu> "Arthur

J. O'Dwyer" <aj*@nospam.andrew.cmu.edu> writes:

"c:/mystuff/filename.bmp" looks much better as a Windows path.

Many non-Unix implementations support Unix-style paths, even if the
native convention is different.

This works only on the NT/2000/XP versions of Windows. The 95/98/ME
versions do not accept the forward slashes.

As argument to the fopen function, such path specifications work since
MSDOS.

Dan
--
Dan Pop
DESY Zeuthen, RZ group
Email: Da*****@ifh.de

[Joe Wright]

Kris Wempa wrote:

"Dan Pop" <Da*****@cern.ch> wrote in message
news:bm**********@sunnews.cern.ch...

In <Pi***********************************@unix46.andr ew.cmu.edu> "Arthur

J. O'Dwyer" <aj*@nospam.andrew.cmu.edu> writes:

"c:/mystuff/filename.bmp" looks much better as a Windows path.

Many non-Unix implementations support Unix-style paths, even if the
native convention is different.

This works only on the NT/2000/XP versions of Windows. The 95/98/ME
versions do not accept the forward slashes.

Not true. Even DOS 6.22 accepted forward slashes. It is COMMAND.COM
which doesn't.
--
Joe Wright http://www.jw-wright.com
"Everything should be made as simple as possible, but not simpler."
--- Albert Einstein ---

[Arthur J. O'Dwyer]

On Thu, 9 Oct 2003, Dan Pop wrote:

"Kris Wempa" <calmincents(NO_SPAM)@yahoo.com> writes:

"Dan Pop" <Da*****@cern.ch> wrote in message

"c:/mystuff/filename.bmp" looks much better as a Windows path.

Many non-Unix implementations support Unix-style paths, even if the
native convention is different.

This works only on the NT/2000/XP versions of Windows. The 95/98/ME
versions do not accept the forward slashes.

As argument to the fopen function, such path specifications work since
MSDOS.

Depends on your implementation of fopen(), doesn't it now? ;-)
(Yes, I think whatever DOS service that was allowed forward slashes,
but it's implementation-defined whether fopen() uses the DOS services ;-)

And besides, you might want to do other things with a filename
besides open it -- like, for instance, passing it to system().
And then if system() uses COMMAND.COM, you have problems.

-Arthur

[Mike Wahler]

"Kris Wempa" <calmincents(NO_SPAM)@yahoo.com> wrote in message
news:bm*********@kcweb01.netnews.att.com...

"Dan Pop" <Da*****@cern.ch> wrote in message
news:bm**********@sunnews.cern.ch...

In <Pi***********************************@unix46.andr ew.cmu.edu> "Arthur

J. O'Dwyer" <aj*@nospam.andrew.cmu.edu> writes:

"c:/mystuff/filename.bmp" looks much better as a Windows path.

Many non-Unix implementations support Unix-style paths, even if the
native convention is different.

This works only on the NT/2000/XP versions of Windows. The 95/98/ME
versions do not accept the forward slashes.

<OT>

All of mine certainly do (my Windows side of the room
has various machines running 95B, 98SE, NT4, and XP)

</OT>

-Mike

[Kris Wempa]

"Dan Pop" <Da*****@cern.ch> wrote in message
news:bm**********@sunnews.cern.ch...

In <bm*********@kcweb01.netnews.att.com> "Kris Wempa" <calmincents(NO_SPAM)@yahoo.com> writes: As argument to the fopen function, such path specifications work since
MSDOS.

Perhaps the forward slashes work for fopen(), but they don't currently work
if used in a system() call. This caused some problems in the past for a
Java applets that were trying to run certain commands based upon the
operating system. Windows 2000/NT accepted the forward slashes, but Windows
95 did NOT.

[Dan Pop]

In <Pi**********************************@unix45.andre w.cmu.edu> "Arthur J. O'Dwyer" <aj*@nospam.andrew.cmu.edu> writes:

On Thu, 9 Oct 2003, Dan Pop wrote:

"Kris Wempa" <calmincents(NO_SPAM)@yahoo.com> writes:

>"Dan Pop" <Da*****@cern.ch> wrote in message
>>
>> "c:/mystuff/filename.bmp" looks much better as a Windows path.
>>
>> Many non-Unix implementations support Unix-style paths, even if the
>> native convention is different.
>
>This works only on the NT/2000/XP versions of Windows. The 95/98/ME
>versions do not accept the forward slashes.
As argument to the fopen function, such path specifications work since
MSDOS.

Depends on your implementation of fopen(), doesn't it now? ;-)

Indeed: one can conceive an implementation accepting *only* the forward
slashes ;-) But we're talking about the *real* implementations for DOS.
(Yes, I think whatever DOS service that was allowed forward slashes,
but it's implementation-defined whether fopen() uses the DOS services ;-)
It doesn't matter, as long as all known C implementations for DOS support
it ;-)
And besides, you might want to do other things with a filename
besides open it -- like, for instance, passing it to system().
And then if system() uses COMMAND.COM, you have problems.

system() is the only standard library function where the rules are
different. But the context of the thread was <stdio.h>...

Dan
--
Dan Pop
DESY Zeuthen, RZ group
Email: Da*****@ifh.de

[Dan Pop]

In <bm*********@kcweb01.netnews.att.com> "Kris Wempa" <calmincents(NO_SPAM)@yahoo.com> writes:

"Dan Pop" <Da*****@cern.ch> wrote in message
news:bm**********@sunnews.cern.ch...

In <bm*********@kcweb01.netnews.att.com> "Kris Wempa"

<calmincents(NO_SPAM)@yahoo.com> writes:

As argument to the fopen function, such path specifications work since
MSDOS.

Perhaps the forward slashes work for fopen(), but they don't currently work
if used in a system() call.

Who was talking about system() calls?

Dan
--
Dan Pop
DESY Zeuthen, RZ group
Email: Da*****@ifh.de

[cjw]

Thanks. Both versions worked. I have program files and data files in
two different directories at the same level. Is there a short form of
specifying it rather than giving the full directory path?
cjw

"Arthur J. O'Dwyer" <aj*@nospam.andrew.cmu.edu> wrote in message news:<Pi***********************************@unix46 .andrew.cmu.edu>...

On Wed, 8 Oct 2003, cjw wrote:

Pl help me with this simple question.
I am using an array to store the file name,
eg. char in[] = "filename.bmp"; How can I give the directory
path with the file name?

char in_plus_path[] = "c:\\mystuff\\filename.bmp";
char unix_style[] = "/mystuff/filename.bmp";

What are you really trying to do?

-Arthur

[Dan Pop]

In <de*************************@posting.google.com> s2******@student.rmit.edu.au (cjw) writes:

Thanks. Both versions worked. I have program files and data files in
two different directories at the same level. Is there a short form of
specifying it rather than giving the full directory path?

You can use relative paths. If your current working directory is the
parent directory of both the data directory and the program directory,
you can use something like: "data/file001.dat" and "prog/program1.exe".

Particularly useful in relative paths on certain systems (Unix and Windows
included) is the ".." thing which stands for the parent directory. In the
context of the previous example, assume that your current working
directory is prog and you want to specify the relative path of
file001.dat: "../data/file001.dat". You can use .. multiple times, to go
further backwards: "../../../foo/bar/baz.dat".

Dan
--
Dan Pop
DESY Zeuthen, RZ group
Email: Da*****@ifh.de