From: <sten.kristian.ivarsson@gmail.com>
To: <cygwin@cygwin.com>
Subject: Sv: Sv: Sv: g++ and c++17 filesystem
Date: Fri, 20 Nov 2020 17:11:06 +0100 [thread overview]
Message-ID: <000601d6bf57$c15e21c0$441a6540$@gmail.com> (raw)
In-Reply-To: <cb35f8af-ee81-aed3-9bd5-ffc84fdb34ac@SystematicSw.ab.ca>
[snip]
> > Applications might wanna extract type, name, parent-folder, etc but do
> > rarely care about what kind of separator it has (/ or \) and the style
> > of the root directory etc and it would be very neat if the cygwin
> > std::filesystem-library became more agnostic in these regards
> Not a goal of this project, which is to provide Unix look/feel at all
> levels.
Well, "this project" have already introduced some understanding of Windows-paths such as ("C:/" etc)
> Other projects have the goals of being cross-platform toolkits which you
> can use to work and/or look native and hide all differences; see:
>
> https://en.wikipedia.org/wiki/Cross-platform_software#Cross-
> platform_programming_toolkits_and_environments
>
> Which cross-development libraries/tools are you missing from the 400
> mingw64 cross-development library and tool packages available for each
> architecture under Cygwin?
Well, some standardized things for networking, ipc-messaging, multiplexing and such is what's missing in the C/C++ standard but we're not missing anything among libraries and tools in the Cygwin package per say
Our main target is the *nix world and thus "Unix look/feel" is exactly what we like and Cygwin seems to offer a "Unix look/feel" to run our code natively on Windows as well but this "Unix look/feel" doesn't always work in Windows and fails to assimilate that "Unix look/feel"
[1] std::filsystem::path path{some_path_from_somewhere};
[2] if(std::filesystem::exists(path))
[3] {
[4] auto canonical = std::filsystem::canonical(path);
[5] }
The code above is very much "Unix look/feel" but the behaviour in Cygwin is not "Unix look/feel" because it might fail on line 4 (complaining that path is not a valid file despite it said so in line 2)
Best regards,
Kristian
> --
> Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
>
> This email may be disturbing to some readers as it contains too much
> technical detail. Reader discretion is advised.
> [Data in binary units and prefixes, physical quantities in SI.]
>
>
> --
> 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
next prev parent reply other threads:[~2020-11-20 16:11 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 ` sten.kristian.ivarsson [this message]
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='000601d6bf57$c15e21c0$441a6540$@gmail.com' \
--to=sten.kristian.ivarsson@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).