public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "René Berber" <rene.berber@gmail.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Sv: g++ and c++17 filesystem
Date: Wed, 18 Nov 2020 10:24:38 -0600	[thread overview]
Message-ID: <c2d6280c-26e3-f9e7-89bd-693385a768b2@gmail.com> (raw)
In-Reply-To: <001701d6bd89$53312ff0$f9938fd0$@gmail.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

  reply	other threads:[~2020-11-18 16:24 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 [this message]
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
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=c2d6280c-26e3-f9e7-89bd-693385a768b2@gmail.com \
    --to=rene.berber@gmail.com \
    --cc=cygwin@cygwin.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).