From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lj1-x229.google.com (mail-lj1-x229.google.com [IPv6:2a00:1450:4864:20::229]) by sourceware.org (Postfix) with ESMTPS id 45CC2385800A for ; Wed, 18 Nov 2020 09:00:59 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 45CC2385800A Received: by mail-lj1-x229.google.com with SMTP id v20so1478587ljk.8 for ; Wed, 18 Nov 2020 01:00:59 -0800 (PST) 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:content-language :thread-index; bh=0gw1N941LiqP3b2bMj+lVnDo/tz2NcUBf2PZK1oPNvk=; b=rYtt1YCkIpRjIn10o6vOttb73aMFVB1mYBeGwxjkjLrNdSzlX09cV6D7JfP4QawwJu NULmr4/Vdbn0BLrcf7kyHuVoXgbVAsK8bqCrGYVpmTudt5HxtvT22tNHOxoGUQtm2B0I ubtpXRwST1EPBcAnnyTdzGBP1yFCsor/bZrvU7GF4kwqzKFXmv/3aQMaUu+kcve6uhWJ 6UngzH69BstFm1P0MQcjjowF2q+lHO3bDR345L4uoz3oA6GGLJAprnIqIpiIOLQI5TvV iJ+2NYpqGjdzCKVGBl9VOH32gzN11Px5hrw88Gbn7Vi05iPLDhq6txTMWKZMGjAGIUuy 8p1g== X-Gm-Message-State: AOAM532VXEuHhD2q0NwQXl1qQHlHgd43KLHlXSTrzBa2vHHUPZ7zjlHf 9QxZge8BJc1u1bcVQXtCvs9QMMOcgI8= X-Google-Smtp-Source: ABdhPJy48/amiGpx8l6+Ms9rqQoMwPXS+ZRBNKYohcAifZfBbuBGXhDVybFcUgNjFNkBgnBvW0p1nA== X-Received: by 2002:a2e:8792:: with SMTP id n18mr3683205lji.57.1605690056384; Wed, 18 Nov 2020 01:00:56 -0800 (PST) Received: from JOKK (87-249-176-245.ljusnet.se. [87.249.176.245]) by smtp.gmail.com with ESMTPSA id 17sm3512903lfr.52.2020.11.18.01.00.55 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 18 Nov 2020 01:00:55 -0800 (PST) From: To: Cc: =?iso-8859-1?Q?'Ren=E9_Berber'?= References: <000001d6bcf4$736e0300$5a4a0900$@gmail.com> <11aad449-bcce-5dd3-8ebf-c751e18b5623@gmail.com> In-Reply-To: <11aad449-bcce-5dd3-8ebf-c751e18b5623@gmail.com> Subject: Sv: g++ and c++17 filesystem Date: Wed, 18 Nov 2020 10:00:55 +0100 Message-ID: <001701d6bd89$53312ff0$f9938fd0$@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 16.0 Content-Language: en-gb Thread-Index: AQHKWLeqweixRSmrC0T+a8DQvHBrLAIbTLjwqdWA85A= X-Spam-Status: No, score=-3.1 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@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Nov 2020 09:01:00 -0000 > 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 ? 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" ? 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 Best regards, Kristian > -- > R.Berber > -- > 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