Thread: ifstream files

Originally Posted by dwks

I would prefer, however, to supply "./" or no path...

Bzuh? Windows uses ".\", even though "./" works

Finally, from my limited experience with Microsoft Visual C++, I think it puts your executable in a Debug/ or Release/ subdirectory of the main project directory, depending on which mode you compiled the program in.

Nope. It puts them in the "Debug\" and "Release\" by default
But it's possible to change this. I typically specify...
$(SolutionDir)Application\$(ConfigurationName)
...as output directory.
Which defaults to something like (Path_to_your_solution)\Application\Debug.
There are my app including any dlls and such it may need. So it isn't littered by all the intermediate files (which are placed in the intermediate directory by default. Handy.

You could try using "../input.in" or copying/moving the input file to this subdirectory.

Nope, that would be "..\input.in"

Oh really? http://www.thescripts.com/forum/thread23123.html

I tend to use forward slashes for directory separators all of the time, because they work in Linux and UNIX and similar systems, and in Windows as well. Even Mac OS X supports them.

This reminds me that another thing to look out for between windows and macs, is filename sensitivity. Mac and other UNIX systems, use case-sensitive filenames. So it is a good idea to reference files exactly as they are named. It is also good idea to use a forward slash (/) to separate directories. It seems that all systems windows, mac, and linux understand / as the directory separator, but only windows understands backslash (\).

From http://forums.rpgdx.net/viewtopic.ph...1bbddfd8016dbf

Another excellent reason to use forward slashes is that you don't have to escape them with \\ all of the time in your code.

More information about where MSVC puts its executables: http://cboard.cprogramming.com/showthread.php?t=99193

I never said Windows didn't support them. It does, but translates them to "\" instead.
And I really, really hate "/". It looks disgusting IMHO. So I always use "\".
Windows API supports "/", but not anything else, so don't go using "/" with system().

Originally Posted by Elysia

I never said Windows didn't support them.

No, but you sort of implied it with all of those "nope"s.

It does, but translates them to "\" instead.

How do you know? I would think someone, somewhere, just used

Code:

if(c == '\\' || c == '/') {
    /* ... */
}

And I really, really hate "/". It looks disgusting IMHO. So I always use "\".

I'm just the opposite, but that's because I use Linux all of the time. I guess you never use Linux, or you'd know what a pain it is to convert slashes . . . .

Windows API supports "/", but not anything else, so don't go using "/" with system().

Well, and the standard C and C++ libraries.

Originally Posted by dwks

No, but you sort of implied it with all of those "nope"s.

I did that because Windows filesystem uses "\" and I really don't like "/"

How do you know? I would think someone, somewhere, just used

Code:

if(c == '\\' || c == '/') {
    /* ... */
}

Because it's documented on MSDN. All Windows API translates "/" to "\" for paths.

I'm just the opposite, but that's because I use Linux all of the time. I guess you never use Linux, or you'd know what a pain it is to convert slashes . . . .

I'll tell you, I'd go mad with the Linux filesystem instead of getting used to it.

Because it's documented on MSDN. All Windows API translates "/" to "\" for paths.

Well, that may be so, but you didn't say that the Windows API did the translation; you said that Windows did the translation, which is different. And of course, I wasn't sure how you'd be able to tell how Windows did things, being closed source as it is.

Besides, though Windows comes up a lot in this thread, I don't think the OP ever says that they use Windows. (I may have missed an implied reference in my quick scan.) Thus, my use of forward slashes is an even better idea. (Of course, I was talking about MSVC for some of my post, but not all of it.)

And we've been ignoring this:

Another excellent reason to use forward slashes is that you don't have to escape them with \\ all of the time in your code.

It's a big factor, it really is.

Originally Posted by dwks

Besides, though Windows comes up a lot in this thread, I don't think the OP ever says that they use Windows. (I may have missed an implied reference in my quick scan.) Thus, my use of forward slashes is an even better idea. (Of course, I was talking about MSVC for some of my post, but not all of it.)

I did a quick scan as well, but decided to go ahead with it because you mentioned Windows first.

It's a big factor, it really is.

Nah. I typically use a utility to convert paths. And I don't really write much absolute paths anyway, so it's not really a big factor.
"/" for directories is just wrong

Originally Posted by robatino

...especially since AFAIK "/" is always on the same key as "?" on the keyboard, but "\" isn't as easy to reach, not to mention it's not always in the same place.

Is not.
"\" is on the same key as "?".
"/" is on key "7".
Ohohohoho!

And what country is that?

Is not.
"\" is on the same key as "?".
"/" is on key "7".
Ohohohoho!

With standard US keyboards, / and ? share the same key. SHIFT-7 is &. http://upload.wikimedia.org/wikipedi...oAltGr.svg.png

It looks like you're using a Spanish keyboard, am I right? http://upload.wikimedia.org/wikipedi...erican.svg.png

Details: http://en.wikipedia.org/wiki/Keyboard_layout#QWERTY

Basically, in DOS, "/" was already being used for something else, so they reluctantly decided to use "\" instead. Other than that, there was no good reason for it, especially since AFAIK "/" is always on the same key as "?" on the keyboard, but "\" isn't as easy to reach, not to mention it's not always in the same place.

Plus "\" was invented because they didn't feel like using alternative notation like "|" or "&".

I did a quick scan as well, but decided to go ahead with it because you mentioned Windows first.

Aha, I found it. The OP actually mentioned it first.

I'm using Microsoft Visual C++ to build the program

My search only searched the text of my reply, as usual, not the whole thread. Sigh.

Indeed, but US uses a weird keyboard in itself.
And of course it's easy to reach.
US keyboards are not standard, so don't go assuming everyone has a similar keyboard.