X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 26F26385480F
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1605773431;
	bh=zVnInMZKKKWuUGj3Tkb0ZmvBvrtCryaJ3RMRLjjNNi4=;
	h=To:References:In-Reply-To:Subject:Date:List-Id:List-Unsubscribe:
	 List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc:
	 From;
	b=xpxF8NgID0P8hdoCjngS8JOwmc0zvV01A+mJx+N+XEJ2KlIocVoiyJNwFzGVKHkCA
	 Uwvauz+UIG2GKjR2eQ5bYogQknvUUgdZFADOw2VTomiYDhX2T8OvCIITNOjSvFxcDV
	 dE2WVzFHVM+KtpQyiWhrZRAWD/UumsEAOHu/NwMM=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org E912A3854828
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date
 :message-id:mime-version:content-transfer-encoding:thread-index
 :content-language;
 bh=YefPBtWmYmLQteShqkn/IkzCUZij6e+byVzAYEX2Ez0=;
 b=M24SMuiCChCZ6no018y8Kclu2KJV+DZTHSAGRry/1h1z13+Eamm3ckU5Vkp7j/m5Tv
 9wQbom/6qPrzI+HDedNLLDVM7SU77UH5yLHTXZHKzocw2mM8huIXwVacj7BIWvqwe+v5
 0GF8/nf6ziQTKJq+WBC4chIDbjG+GgLAjpTlw/A12ZiaBlwhlbM/UzkEPWt8d2HaEwlP
 eyX+GT2OszKWJU1Kjn+VBvLYP06WRssK0wC2Te+CnVH9zOE9TPefNww7ipigZzRvJM8Q
 i44uJhe7a0XV3l6qIKAKthmBqWeMHxgbpzZNZAXQSt+mpgdwt6NtAWAkiIuMEpnye12G
 9rng==
X-Gm-Message-State: AOAM530zFwG5Z23TzrBabRhsSlW2G7MmOZWDjIe+eyrdxOKCv4pI5Il3
 3FrqHVVZvIi70Wov3NN546Zqmei8Hwc=
X-Google-Smtp-Source: ABdhPJz/P6h+HYt0Vig123O5CY5YCUuXmaZjPeg0xwW/Q3gC9gT81srGATqbtV4vSuE9FU0AO/TsOg==
X-Received: by 2002:a05:6512:3af:: with SMTP id
 v15mr5069899lfp.144.1605773426655; 
 Thu, 19 Nov 2020 00:10:26 -0800 (PST)
To: <moss AT cs DOT umass DOT edu>
References: <861bc601-876b-e16d-d4f7-0bb543d61d8e AT cs DOT umass DOT edu>
 <FD1969EA-9204-4986-BE5E-0C9F45D256B7 AT gmail DOT com>
 <d3a237ab-d237-bc16-ca1c-48337dc6bff8 AT cs DOT umass DOT edu>
In-Reply-To: <d3a237ab-d237-bc16-ca1c-48337dc6bff8@cs.umass.edu>
Subject: Sv: g++ and c++17 filesystem
Date: Thu, 19 Nov 2020 09:10:25 +0100
Message-ID: <000901d6be4b$6fb780d0$4f268270$@gmail.com>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQIlP1SugCLya2e1VV8YxFv4djZhVwG6+jwAAtnD4a6pDW7LsA==
Content-Language: en-gb
X-Spam-Status: No, score=-3.0 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
Cc: cygwin AT cygwin DOT com,
        "=?utf-8?Q?'Ren=C3=A9_Berber'?=" <rene DOT berber AT gmail DOT com>
Content-Type: text/plain; charset="utf-8"
Sender: "Cygwin" <cygwin-bounces AT cygwin DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 0AJ8AxGl027913

> >> I would agree that if you want an executable that acts and feels more
> like a Windows native application, then mingw is probably what you want.
> Cygwin is if you want something that acts and feels more like a Posix
> thing ... which means it will be oriented to Posix style paths.
> > To be able to use mingw all the code have to be ported to use Windows
> > native mechanisms and then we might just use MSVC instead
> >
> > We don’t want (either) Windows-style-paths or Posix-style-paths, we
> > want A path and expect it to work equally regardless of what platform
> > is used in regards to std::filesystem
> >
> > As far as I see, very few applications do form their own - and/or have
> > hard-coded absolute paths and instead they are usually input data
> > (through UI, configuration, OS, environment or such)
> 
> IN this context, I would say "Which std::filesystem?  The Cygwin Posix-
> like one or the mingw Windows-like one?"  If you want uniformity, I'd go
> with Cygwin; it you want platform-like behavior, then mingw.


I'm referring to std::filesystem as a part of the C++17 standard (https://en.cppreference.com/w/cpp/filesystem) that is pretty well defined and quite agnostic to what "style" of path used as our application are and as I said, we don't care (we don't ever inspect them) what "style" of paths we're using but we expect a deterministic behaviour from that library regardless of operating system, such as and absolute path should be an absolute path regardless

That's the sole purpose of std::filesystem, i.e. to be platform independent (though all file-features is not applicable on all operating systems, but at least you can ask the library for those attributes)


GCC/MinGW support platform-INDEPENDENT-behaviour because gcc/g++ works equally regardless if Linux or Windows in regards to std::filesystem


Best regards,
Kristian


> Best wishes - EM
> --
> 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