DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org F207E3851C2E
Subject: Re: Sv: g++ and c++17 filesystem
References: <000001d6bcf4$736e0300$5a4a0900$@gmail.com>
 <11aad449-bcce-5dd3-8ebf-c751e18b5623@gmail.com>
 <001701d6bd89$53312ff0$f9938fd0$@gmail.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Message-ID: <c2d6280c-26e3-f9e7-89bd-693385a768b2@gmail.com>
Date: Wed, 18 Nov 2020 10:24:38 -0600
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.19)
 Gecko/20081209 Lightning/0.9 Thunderbird/2.0.0.19 Mnenhy/0.7.6.0
MIME-Version: 1.0
In-Reply-To: <001701d6bd89$53312ff0$f9938fd0$@gmail.com>
Content-Language: en-US
Precedence: list
From: =?utf-8?q?Ren=C3=A9_Berber_via_Cygwin?= <cygwin@cygwin.com>
Reply-To: cygwin@cygwin.com
Cc: =?UTF-8?Q?Ren=c3=a9_Berber?= <rene.berber@gmail.com>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: cygwin-bounces@cygwin.com
Sender: "Cygwin" <cygwin-bounces@cygwin.com>

On 11/18/2020 3:00 AM, Kristian Ivarsson via Cygwin wrote:

>> 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 ?

I'm not saying anything, I'm pointing to the relevant documentation.

> 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" ?

The documentation states that using Windows notation is not supported 
and may result in unexpected results (i.e. sometimes work, sometimes 
doesn't).

> 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

The problem is that your assumptions and expectations are wrong.  Not 
knowing Cygwin that is expected.

Cygwin handles the file system with no problem, but using Posix-like 
notation, not Windows-like.  End of story.
--
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