From: ludo@gnu.org (Ludovic Courtès)
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel@gnu.org
Subject: Re: [Guile-commits] GNU Guile branch, stable-2.0, updated. v2.0.0-4-g3e05fc0
Date: Tue, 22 Feb 2011 12:36:56 +0100 [thread overview]
Message-ID: <87lj18s3l3.fsf@gnu.org> (raw)
In-Reply-To: <m3pqqlxez6.fsf@unquote.localdomain> (Andy Wingo's message of "Mon, 21 Feb 2011 22:19:41 +0100")
Hello,
Andy Wingo <wingo@pobox.com> writes:
> On Mon 21 Feb 2011 21:50, ludo@gnu.org (Ludovic Courtès) writes:
>
>>> --- a/libguile/ports.c
>>> +++ b/libguile/ports.c
>>> @@ -661,6 +661,19 @@ scm_i_remove_port (SCM port)
>>> scm_port_non_buffer (p);
>>> p->putback_buf = NULL;
>>> p->putback_buf_size = 0;
>>> +
>>> + if (p->input_cd != (iconv_t) -1)
>>> + {
>>> + iconv_close (p->input_cd);
>>> + p->input_cd = (iconv_t) -1;
>>> + }
>>> +
>>> + if (p->output_cd != (iconv_t) -1)
>>> + {
>>> + iconv_close (p->output_cd);
>>> + p->output_cd = (iconv_t) -1;
>>> + }
>>> +
>>
>> I don’t think this is needed: each port has a finalizer,
>> ‘finalize_port’, which normally takes care of this, eventually.
>
> It is needed, but only in the case that you `close-port' explicitly.
> The block in finalize_port only takes care of gc'd open ports.
Right. Closed ports are eventually GC’d, so in that sense it is not
strictly needed, but OK.
Valgrind was wrong! ;-)
Ludo’.
next prev parent reply other threads:[~2011-02-22 11:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1PqVCx-0003xM-4I@vcs-noshell.in.savannah.gnu.org>
2011-02-21 20:50 ` [Guile-commits] GNU Guile branch, stable-2.0, updated. v2.0.0-4-g3e05fc0 Ludovic Courtès
2011-02-21 21:19 ` Andy Wingo
2011-02-22 11:36 ` Ludovic Courtès [this message]
2011-02-22 19:11 ` Andy Wingo
2011-02-22 20:35 ` Ludovic Courtès
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=87lj18s3l3.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
--cc=wingo@pobox.com \
/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).