Boost::filesystem: Updating from 1.34.1 to current?

Boost::filesystem defines two formats for filenames: native, which differs from system to system, and generic which is identical across systems. Under POSIX (which appears to be what you are using) the two are identical. Under Windows the native format allows backslashes whereas the generic format does not.

Under VMS (for example) the two are very different (the native format is something like dir. Subdirfile ).

Boost::filesystem defines two formats for filenames: native, which differs from system to system, and generic which is identical across systems. Under POSIX (which appears to be what you are using) the two are identical. Under Windows the native format allows backslashes whereas the generic format does not.

Under VMS (for example) the two are very different (the native format is something like dir. Subdirfile). Boost::filesystem::native appears to have been intended to indicate that the filename you are providing is in native format.

I believe the current version of boost::filesystem is supposed to decide automatically, and since you're on a POSIX system it makes no difference anyway. In short, the correct thing to do is simply to omit the parameter.

That was quite helpful, and would've earned a "correct answer" checkmark if I hadn't been too foggy about the requirements. See updated question. – DevSolar Apr 6 at 14:43.

Native seems to be a function now and the path constructor doesn't seem to need the native specifier. So just removing it should be fine.

See updated question; sorry for not being clearer from the start. – DevSolar Apr 6 at 14:43.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.