From: Kevin Ryde <user42@zip.com.au>
Cc: bug-guile@gnu.org
Subject: Re: CVS-060720 compilation failure on Mac OS X 10.4, patch (dirfd)
Date: Tue, 25 Jul 2006 10:52:43 +1000 [thread overview]
Message-ID: <87wta2ld44.fsf@zip.com.au> (raw)
In-Reply-To: <44BF8E9F.6090409@student.liu.se> (Claes Wallin's message of "Thu, 20 Jul 2006 16:09:35 +0200")
Claes Wallin <clawa570+gmane@student.liu.se> writes:
>
> * test-suite/tests/dirfd.test:
> Since dirfd is used by readdir on platforms that have it, this test
> does an opendir and two consecutive readdirs, expecting "." and "..".
> Not sure if this works on non-posix platforms.
Yep, not sure about "." and "..", though I remember most unixy stuff
on DOS systems synthesising them in the bad old days. There's an
existing test in filesys.test when expects the root directory "/" to
be non-empty; it at least exercises the opendir/readdir/closedir
sequence.
Perhaps a test that created a long-named temporary file (in the
builddir) would be an idea. But might have to communicate the
NAME_MAX (or equivalent) size to the scheme level to do that
effectively.
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
prev parent reply other threads:[~2006-07-25 0:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-20 14:09 CVS-060720 compilation failure on Mac OS X 10.4, patch (dirfd) Claes Wallin
2006-07-20 23:58 ` Kevin Ryde
2006-07-21 6:36 ` Claes Wallin
2006-07-21 7:36 ` Claes Wallin
2006-07-25 0:52 ` Kevin Ryde [this message]
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wta2ld44.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=bug-guile@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).