X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org 335FB3945060
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1606228275;
	bh=CK1AvOqNosW0ep4RC0Cfqv0JkthZzp1J5y6T+gMeJR8=;
	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=L8MLyBthT/Nyrt6Jc7d5Cu9hMG1+fIKWjzfQzS1/0Uu6e99v0jfWpFC9W3WFg2boS
	6rvdXyXO+j+QUayZyjQ/St3Qhjno2UggYFqwDyaDQot3Vyku3J4Bkt+ZmMI/kKE5al
	EIfAvje7vuRcgmaktYBFVDHjBfbVYgi4qrid1CQk=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.3.2 sourceware.org 07E1E3944835
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:thread-index
	:content-language;
	bh=DDeYoocQZI1u7yrgwVsRhhpLuOqov74EXoN3iakYX6M=;
	b=bfluJrLQB714d5kL8kjPWdDVvaeFjIZAr4rT1Ac8LPB7+ENL2PuB03zLXG86p4X+3a
	Uu89cPg8crTZaALH17qn8GGgyS2MPgo+jfJM4q9LWxXb2RW3ZYP4SRVmavgSSYNJUAxv
	sfdTZ7xvu6VTV32YDZ+PkwS8AxxvsMHGPMrAYfIbQfmZrDV70eZC+eVRo5m8rQ7xQwrW
	vrpyTGWM4RgefS5esCZX/dyLaqYYcznprcF2+zW1AmFxLgNA1f8MzAOtKIkOfm7XV35D
	1keDgArEvavFaZSeNmatH/mNxru9iZo7gMyDjtOlsxIG22tRzkARjV7ftB1hprdyUNHR
	4QwA==
X-Gm-Message-State:	AOAM5320iN6NAcSxN0ux2RK30UsxvFDP65l42Yw164wrhUrAeWTpOTJq
	rIDBt8j5NSX818eZoAkSK24=
X-Google-Smtp-Source:	ABdhPJxkSoqsaMEvk5ivS7lq7zLB8y6gOT/wjcDjVnLt/yGfP9D1YmW+OBSHDPnme9dhymKBX/vW/Q==
X-Received:	by 2002:a2e:9b58:: with SMTP id o24mr2136022ljj.84.1606228270888;
	Tue, 24 Nov 2020 06:31:10 -0800 (PST)
To:	<moss AT cs DOT umass DOT edu>, "'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>
	<237eacd5-a1bf-da6a-2ee6-f2df945f125b AT cs DOT umass DOT edu>
In-Reply-To:	<237eacd5-a1bf-da6a-2ee6-f2df945f125b@cs.umass.edu>
Subject:	Sv: Sv: Sv: Sv: Sv: g++ and c++17 filesystem
Date:	Tue, 24 Nov 2020 15:31:08 +0100
Message-ID:	<000501d6c26e$73e1d760$5ba58620$@gmail.com>
MIME-Version:	1.0
X-Mailer:	Microsoft Outlook 16.0
Thread-Index:	AQIMEcHDzo+EBBrhHHj3sFlr53GwtQIBqNbVAy9h9QUA3PghxQI7mYCPAhTJa9sCXpfa/AHDfHWzAafgnf4Bf6X0yKjfdQCg
X-Spam-Status:	No, score=-2.3 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
Sender:	"Cygwin" <cygwin-bounces AT cygwin DOT com>

> 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 we keep talking at cross purposes.


Maybe it is the right thing to do, but what is your take of why it must be so (all the way) ?

I also do understand that it have several advantages in the implementation of std::filesystem but it also imply an extra layer of abstraction to the underlaying platform, but to just remove the _CYGWIN_ macro when building it would make std::filesystem to not understand /cygdrive at all (and I guess that would confuse other users;-) so I guess it would require some more sophisticated implementation (or extend the number of exceptions already existing in the underlaying Cygwin-Posix-implementation)

Best regards,
Kristian

> Best wishes - Eliot Moss

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

- Raw text -