From: Jonathan Yong <10walls@gmail.com>
To: sten.kristian.ivarsson@gmail.com,
'The Cygwin Mailing List' <cygwin@cygwin.com>
Subject: Re: Sv: Sv: Sv: Sv: Sv: g++ and c++17 filesystem
Date: Tue, 24 Nov 2020 12:33:27 +0000 [thread overview]
Message-ID: <2d906235-e206-f6c6-5302-9b11bbe484c7@gmail.com> (raw)
In-Reply-To: <001801d6c255$f0e115a0$d2a340e0$@gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 2327 bytes --]
On 11/24/20 11:35 AM, sten.kristian.ivarsson@gmail.com wrote:
> [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
>
How do you expect std::filesystem to do that when Windows paths are not
even accepted in API calls?
>> 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
Why would std::filesystem be an exception? How would it know if a
backslash is part of a name and not a separator? How does it know when
to apply exceptions? What about mixed paths?
The C++ standard mentions separators, not specific characters, and the
forward slash is used under Cygwin, not the Windows backslash.
The bigger question would be how would you expect a Cygwin application
to even accept a Windows paths. It should use *nix paths, as all Cygwin
programs do.
[-- Attachment #1.1.2: OpenPGP_0x713B5FE29C145D45_and_old_rev.asc --]
[-- Type: application/pgp-keys, Size: 8035 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2020-11-24 12:33 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 15:15 sten.kristian.ivarsson
2020-11-17 16:45 ` René Berber
2020-11-18 9:00 ` Sv: " sten.kristian.ivarsson
2020-11-18 16:24 ` René Berber
2020-11-18 16:31 ` Eliot Moss
2020-11-18 20:46 ` Kristian Ivarsson
2020-11-18 20:56 ` Eliot Moss
2020-11-18 21:18 ` Kristian Ivarsson
2020-11-18 23:47 ` Eliot Moss
2020-11-19 8:10 ` Sv: " sten.kristian.ivarsson
2020-11-18 21:45 ` Norton Allen
2020-11-19 0:08 ` Doug Henderson
2020-11-19 6:23 ` Brian Inglis
2020-11-19 10:03 ` Sv: " sten.kristian.ivarsson
2020-11-19 15:27 ` Brian Inglis
2020-11-20 9:37 ` Sv: " sten.kristian.ivarsson
2020-11-20 15:29 ` Brian Inglis
2020-11-20 16:11 ` Sv: " sten.kristian.ivarsson
2020-11-19 15:36 ` Eliot Moss
2020-11-20 8:31 ` Sv: " sten.kristian.ivarsson
2020-11-20 18:28 ` Jonathan Yong
[not found] ` <000601d6c173$aa55d540$ff017fc0$@gmail.com>
2020-11-23 11:09 ` Sv: " Jonathan Yong
2020-11-24 9:32 ` Sv: " sten.kristian.ivarsson
2020-11-24 10:24 ` Jonathan Yong
2020-11-24 11:35 ` Sv: " sten.kristian.ivarsson
2020-11-24 12:33 ` Jonathan Yong [this message]
2020-11-24 14:01 ` Sv: " sten.kristian.ivarsson
2020-11-25 2:25 ` Jonathan Yong
2020-11-24 13:22 ` Eliot Moss
2020-11-24 14:31 ` Sv: " sten.kristian.ivarsson
2020-11-24 20:06 ` Ken Brown
2020-11-24 20:39 ` Eliot Moss
2020-11-25 8:02 ` Sv: " sten.kristian.ivarsson
2020-11-25 8:30 ` sten.kristian.ivarsson
2020-11-25 0:23 ` Brian Inglis
2020-11-25 9:00 ` Sv: " sten.kristian.ivarsson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2d906235-e206-f6c6-5302-9b11bbe484c7@gmail.com \
--to=10walls@gmail.com \
--cc=cygwin@cygwin.com \
--cc=sten.kristian.ivarsson@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).