Sv: Sv: Sv: Sv: Sv: Sv: g++ and c++17 filesystem

Thanx for the insightful thoughts Ken See more below > >>> all the std::filesystem implementations I've seen for Windows > >> > >> The implementation on top of Cygwin is not "for Windows", it's "for > >> Cygwin", i.e., "for Posix". And for Cygwin that's the right thing to > do. > >> And that's

Sv: Sv: Sv: Sv: Sv: Sv: g++ and c++17 filesystem

> For the specific case C:\Temp, I found this: > > cygpath -ua 'C:\Temp' > >-> /cygdrive/c/Temp > > cygpath -ua /cygdrive/c/Temp > >-> /cygdrive/c/Temp > > cygpath -ua '\Temp' > >-> /cygdrive/c/Temp > > cygpath -ua '/Temp' > >-> /Temp > > Now Cygwin is open source, so you,

Re: Sv: Sv: Sv: Sv: Sv: Sv: g++ and c++17 filesystem

On 11/24/20 2:01 PM, sten.kristian.ivars...@gmail.com wrote: [snip] std::filesystem POSIX mode is common to all POSIX platforms where backslashes are NOT directory separators. How do you make them accept your demands? How are you going to force POSIX platforms allow Windows specific code?

Sv: Sv: Sv: Sv: Sv: Sv: g++ and c++17 filesystem

> > [snip] > > > >> std::filesystem POSIX mode is common to all POSIX platforms where > >> backslashes are NOT directory separators. How do you make them accept > >> your demands? How are you going to force POSIX platforms allow > >> Windows specific code? > > > > I've been trying to say over and