public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bugdal at aerifal dot cx" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/6050] iconv(1) buffers all of stdin in memory
Date: Mon, 07 Oct 2013 14:06:00 -0000	[thread overview]
Message-ID: <bug-6050-131-ORmv7u3LWG@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-6050-131@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=6050

--- Comment #3 from Rich Felker <bugdal at aerifal dot cx> ---
On Mon, Oct 07, 2013 at 01:58:09PM +0000, neleai at seznam dot cz wrote:
> This would work only for stateless encodings. You cannot do this with
> ISO-2022-JP as you would need additional argument to save state.

No, the state is saved in the conversion descriptor, and iconv(3)
reports to the caller the exact point at which it stopped in the
input, so you simply resume from that point.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2013-10-07 14:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-6050-131@http.sourceware.org/bugzilla/>
2012-12-19 10:44 ` schwab@linux-m68k.org
2013-08-10 16:01 ` bugdal at aerifal dot cx
2013-10-07 13:58   ` Ondřej Bílka
2013-10-07 13:58 ` neleai at seznam dot cz
2013-10-07 14:06 ` bugdal at aerifal dot cx [this message]
2013-10-09  7:50 ` neleai at seznam dot cz
2015-08-27 22:03 ` [Bug locale/6050] " jsm28 at gcc dot gnu.org
2024-09-20 11:54 ` fweimer at redhat dot com
2008-04-08 18:47 [Bug libc/6050] New: " skunk at iskunk dot org
2008-04-09  3:04 ` [Bug libc/6050] " drepper at redhat dot com

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=bug-6050-131-ORmv7u3LWG@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.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).