> On 11/17/2020 9:15 AM, Kristian Ivarsson via Cygwin wrote: > > > The filesystem-library as a part of C++17 seems to have some defects > > and flaws in the cygwin-package and pretty much every lexical- and > > canonical operation works in mysterious ways (or not at all) > [snip] > > https://cygwin.com/cygwin-ug-net/using.html#pathnames-win32
So by this you're saying that cygwin-applications cannot handle the filesystem it is supposed to handle ? How come std::filesystem first say "It's a valid file" followed by "It's not a valid file" ? Is that part of the "circumvention" ? In the current use case, the path is even returned from std::filesystem::directory_iterator where it says "Hey, here's a path to a file I found in the folder you pointed out" followed by "The path I just gave to you is not a valid path" It's gonna be tricky to implement applications in that way Best regards, Kristian > -- > R.Berber > -- > Problem reports: https://cygwin.com/problems.html > FAQ: https://cygwin.com/faq/ > Documentation: https://cygwin.com/docs.html > Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple