From: Martin Sebor <msebor@gmail.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: libstdc++ <libstdc++@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch] libstdc++/67173 Fix filesystem::canonical for Solaris 10.
Date: Wed, 16 Sep 2015 22:17:00 -0000 [thread overview]
Message-ID: <55F9E75F.10602@gmail.com> (raw)
In-Reply-To: <20150916185844.GD2631@redhat.com>
> Tested powerpc64le-linux, x86_64-dragonfly4.1 and x86_64-netbsd5.1,
> do you see any reason not to commit this for now?
I see only a couple of potential problems: a missing test for
PATH_MAX in the unlikely event it's not defined (or is obscenely
large), and a missing check to avoid infinite loops due to symlinks.
>
> Any improvements such as hardcoding checks for specific versions of
> Solaris or the BSDs are QoI, and this is only an experimental TS, so I
> don't want to spend the rest of stage 1 working on one function :-)
Makes sense.
> My main obstacle to writing good tests right now is having some way to
> create and destroy files safely in the tests. It's hard to test
> functions like is_symlink() without first creating a symlink in a
> known location, and also removing it again cleanly so the next
> testsuite run doesn't fail if the file is already present.
>
> One option would be to have libstdc++-v3/testsuite/Makefile create a
> new sub-directory as a sandbox for filesystem tests, removing it if it
> already exists. Then the tests can put anything they like in that new
> dir without fear of trashing the user's files elsewhere on the FS!
I don't know how you feel about Tcl but writing a filesystem.exp
and adding a new "dg-fs" API would let each test can set up the
directory structure it needs.
Martin
next prev parent reply other threads:[~2015-09-16 22:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 14:23 Jonathan Wakely
2015-09-11 18:05 ` Martin Sebor
2015-09-12 10:39 ` Jonathan Wakely
2015-09-12 19:49 ` Martin Sebor
2015-09-12 22:00 ` Martin Sebor
2015-09-16 14:52 ` Jonathan Wakely
2015-09-16 16:05 ` Jonathan Wakely
2015-09-16 16:11 ` Jonathan Wakely
2015-09-16 17:38 ` Martin Sebor
2015-09-16 19:02 ` Jonathan Wakely
2015-09-16 22:17 ` Martin Sebor [this message]
2015-09-16 22:23 ` Jonathan Wakely
2015-09-16 23:51 ` Martin Sebor
2015-09-17 11:31 ` Jonathan Wakely
2015-09-17 11:33 ` Jonathan Wakely
2015-09-17 14:38 ` Jonathan Wakely
2015-09-17 15:40 ` Martin Sebor
2015-09-23 12:14 ` Jonathan Wakely
2015-09-16 23:42 ` Jonathan Wakely
2015-09-17 15:36 ` Jonathan Wakely
2015-09-17 19:27 ` Andreas Schwab
2015-09-17 22:23 ` Jonathan Wakely
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=55F9E75F.10602@gmail.com \
--to=msebor@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@redhat.com \
--cc=libstdc++@gcc.gnu.org \
/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).