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

2020-11-25 Thread Kristian Ivarsson via Cygwin
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 w

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

2020-11-25 Thread Kristian Ivarsson via Cygwin
> 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

2020-11-24 Thread Jonathan Yong via Cygwin
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? I'v

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

2020-11-24 Thread Eliot Moss
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, too, could grab the code in cygpath and c

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

2020-11-24 Thread Ken Brown via Cygwin
On 11/24/2020 9:31 AM, Kristian Ivarsson via Cygwin wrote: On 11/24/2020 4:32 AM, Kristian Ivarsson via Cygwin wrote: 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 t

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

2020-11-24 Thread Kristian Ivarsson via Cygwin
> On 11/24/2020 4:32 AM, Kristian Ivarsson via Cygwin wrote: > > > 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 where w

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

2020-11-24 Thread Kristian Ivarsson via Cygwin
> > [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 o

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

2020-11-24 Thread Jonathan Yong via Cygwin
On 11/24/20 11:35 AM, 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? I'

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

2020-11-24 Thread Kristian Ivarsson via Cygwin
[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 over again that our code do