From: Neil Jerram <neil@ossau.uklinux.net>
To: ludo@gnu.org (Ludovic Courtès)
Cc: bug-guile@gnu.org
Subject: Re: guile 1.9.0 scm_read_hash_extend gc trouble
Date: Sat, 27 Jun 2009 22:53:35 +0100 [thread overview]
Message-ID: <8763eh4a3k.fsf@arudy.ossau.uklinux.net> (raw)
In-Reply-To: <86zlby35wx.fsf@gnu.org> ("Ludovic Courtès"'s message of "Wed\, 24 Jun 2009 01\:07\:58 +0200")
ludo@gnu.org (Ludovic Courtès) writes:
> The attached patch adds a new `scm_t_off' type, whose definition does
> not depend on the application's `_FILE_OFFSET_BITS' value. Can you
> confirm that it allows you to build Guile with 32-bit offsets and Snd
> with 64-bit offsets (or vice versa)?
>
> Neil: Does this sound like the right approach?
Yes, this looks great. (In case it makes a difference, I've reviewed
the master commit, not the patch that you put in email.)
Also I think it means that we can delete some code that was needed to
handle the possibility that off_t might be 32-bit on a platform that
also supports large files.
- In scm_seek (), the "if (SCM_OPFPORTP (fd_port))" block is now not
needed, because the following more general "if (SCM_OPPORTP
(fd_port))" case will handle 64-bit correctly.
- Therefore scm_i_fport_seek () can be removed.
- The "#if GUILE_USE_64_CALLS && HAVE_STAT64 && SIZEOF_OFF_T !=
SIZEOF_OFF64_T" implementation of fport_seek () can be removed,
because fport_seek () is now always identical to
fport_seek_or_seek64 ().
- Plus the same things again but for "truncate" instead of "seek".
Would you agree?
Regards,
Neil
next prev parent reply other threads:[~2009-06-27 21:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-21 12:10 guile 1.9.0 scm_read_hash_extend gc trouble Bill Schottstaedt
2009-06-21 15:34 ` Neil Jerram
2009-06-21 15:56 ` Neil Jerram
2009-06-22 17:23 ` Bill Schottstaedt
2009-06-22 23:25 ` Neil Jerram
2009-06-23 19:18 ` Bill Schottstaedt
2009-06-23 23:07 ` Ludovic Courtès
2009-06-27 21:53 ` Neil Jerram [this message]
2009-06-27 23:42 ` Ludovic Courtès
2009-06-29 15:02 ` Ludovic Courtès
2009-06-29 19:18 ` Neil Jerram
2009-06-24 10:19 ` Bill Schottstaedt
2009-06-22 8:50 ` Thien-Thi Nguyen
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=8763eh4a3k.fsf@arudy.ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=bug-guile@gnu.org \
--cc=ludo@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).