From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: file-exists? confused
Date: Tue, 14 Mar 2006 08:17:58 +1100 [thread overview]
Message-ID: <877j6y6o3d.fsf@zip.com.au> (raw)
In-Reply-To: <20060313165454.M814@ccrma.Stanford.EDU> (Bill Schottstaedt's message of "Mon, 13 Mar 2006 08:55:49 -0800")
"Bill Schottstaedt" <bil@ccrma.Stanford.EDU> writes:
>
> The new Guile's file-exists? function is confused by very large files:
Ahh. I changed it from access() to stat() to get the perms right
under setuid. I think you'll find you can't open such a file in
guile, so saying it doesn't exist is bad, but not terrible.
I guess we should compile with _FILE_OFFSET_BITS == 64 and make sure
uses of off_t can cope with being either 32 or 64 bits.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2006-03-13 21:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-13 16:55 file-exists? confused Bill Schottstaedt
2006-03-13 21:17 ` Kevin Ryde [this message]
2006-03-14 22:33 ` Kevin Ryde
2006-03-25 22:48 ` Marius Vollmer
2006-03-29 0:45 ` Kevin Ryde
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=877j6y6o3d.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=guile-devel@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).