X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 87EE5393C846
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1606217747;
	bh=G9Zb8RHqnGmYPir5LlZuodAKVsbU2vhr2pN5Y/XYzpY=;
	h=To:References:In-Reply-To:Subject:Date:List-Id:List-Unsubscribe:
	 List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	 From;
	b=Tq/eyTkCiNs7RL7i3UFRBCo8iPMtL7IUmgJImvdvwNZ/r38ah9Hy0aJFznFG2ULzt
	 HYzFH4m3mEr/0qlQRso5vmyBDmpe4MSSsVGxTF8R8fVCiuT0AOX/3rzmnSVLC3vXwm
	 nUu7L6a3NtXh/3S5NmeV3HNZlsFIfgTfYRSX9l5c=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 39EE53844046
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:from:to:references:in-reply-to:subject:date
 :message-id:mime-version:content-transfer-encoding:content-language
 :thread-index;
 bh=LGCldSvb+V/QSVidWDAMfjJ8GPZDxD85rcVJVMiAHS8=;
 b=fCBs9IIkUT6sYXb/3kT8OCljl09XNtVXqunF3lDHwtkUplJ6P48t5WgK9hq6z5Husq
 M/CmUF69z7zfC3MBdahO2cnc/L76NsUpOrLMQq+O60rpR3dCSQwIPrhSfLoxqT/hrhB4
 nE8mvpfiac1+ulFe+3tToxcKIvclrzliQuC7XVCGGRuThLCaXaJI0Z9QLnV7oN8w6cWR
 w4mRJvaoDaQgB/GeSlBk06goAURNOlC4mU0tajt2YVIVweXyWGredrfw/Mr4dXXi3l3h
 fhADWhM0g4w/vKFxQzJ0gf+CUwtKh220y3G6cWERIXGtDUtM//VwREMmy5sfLv0oVfzT
 +zig==
X-Gm-Message-State: AOAM532qzjt6Pri2vmEf2cK4mQ/eDAZ1BXG0a+qxfkOPB1Za0AxEl9NA
 /E/GMxiUcV3sfx5gzq0/xO8=
X-Google-Smtp-Source: ABdhPJwirbMsirL7vi6TBR00ZgQqQS3XdpP1hgOEEh7HiDleg7WxjrdRtOqKKCEmsHqVF4yWbV/BRw==
X-Received: by 2002:ac2:5a46:: with SMTP id r6mr1497857lfn.293.1606217742925; 
 Tue, 24 Nov 2020 03:35:42 -0800 (PST)
To: "'Jonathan Yong'" <10walls AT gmail DOT com>,
        "'The Cygwin Mailing List'" <cygwin AT cygwin DOT com>
References: <c2d6280c-26e3-f9e7-89bd-693385a768b2 AT gmail DOT com>
 <D3704C33-A283-40F0-990D-CB9806F0B09D AT gmail DOT com>
 <000a01d6be5b$3808cad0$a81a6070$@gmail.com>
 <87a2c99c-045c-e815-4c03-bab7a89a025b AT cs DOT umass DOT edu>
 <000201d6bf17$7cc4beb0$764e3c10$@gmail.com>
 <9e881c01-e883-ecd5-883a-e1ac55c740c7 AT gmail DOT com>
 <000601d6c173$aa55d540$ff017fc0$@gmail.com>
 <d8a72610-a79b-0387-e52b-25f0b50c46ef AT gmail DOT com>
 <000a01d6c244$b64bbd70$22e33850$@gmail.com>
 <ec2a7fe8-35c8-21e5-bb6a-687e7968db53 AT gmail DOT com>
In-Reply-To: <ec2a7fe8-35c8-21e5-bb6a-687e7968db53@gmail.com>
Subject: Sv: Sv: Sv: Sv: Sv: g++ and c++17 filesystem
Date: Tue, 24 Nov 2020 12:35:40 +0100
Message-ID: <001801d6c255$f0e115a0$d2a340e0$@gmail.com>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 16.0
Content-Language: en-gb
Thread-Index: AQIMEcHDzo+EBBrhHHj3sFlr53GwtQIBqNbVAy9h9QUA3PghxQI7mYCPAhTJa9sCXpfa/AHDfHWzAafgnf4BRx5CO6jhA9fw
X-Spam-Status: No, score=-2.5 required=5.0 tests=BAYES_00, DKIM_SIGNED,
 DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,
 SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
 server2.sourceware.org
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.29
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From: Kristian Ivarsson via Cygwin <cygwin AT cygwin DOT com>
Reply-To: sten DOT kristian DOT ivarsson AT gmail DOT com
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: "Cygwin" <cygwin-bounces AT cygwin DOT com>

[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 doesn't handle any Windows specific stuff and not anywhere have I claimed that anyone else need to handle Windows specific stuff either (except for the internals of Cygwin of which Windows specific logic is already present)

I repeat; I don't expect any of the Cygwin-Posix-functions to accept any Windows-style-paths (though some of them, as I repeatedly have said, already does so) and I only expect that I can operate according to the C++-standard on an instantiated std::filesystem::path 

> Make it try to enter subdirectories every time std::filesystem is
> called?
> 
> You refuse to understand that Cygwin is NOT Windows, it is a POSIX
> platform. Using Cygwin means complying with POSIX expectations and
> standards.
> 
> I don't see how this conversation can continue if you still refuse to see
> Cygwin as something separate from Windows. Besides, you have already
> answered your question by ruling out MinGW, so Microsoft Visual Studio it
> is.

I repeat (again); neither MinGW/MSVS is an option because we're trying to use Posix and C++

Just to be clear:

- Our code DOESN'T handle Windows-style-paths explicitly in any way
- We DON'T expect Cygwin-Posix-file-related-functions to accept Windows-style-paths
- We WOULD like std::filesystem to work according to the C++ ISO standard


Does that make any sense ? 


Kristian 

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