From: ag <aga.chatzimanikas@gmail.com>
To: Bruno Haible <bruno@clisp.org>
Cc: "Tim Rühsen" <tim.ruehsen@gmx.de>,
"Paul Eggert" <eggert@cs.ucla.edu>,
bug-gnulib@gnu.org
Subject: Re: string types
Date: Sun, 29 Dec 2019 22:02:26 +0200 [thread overview]
Message-ID: <20191229200226.GA13246@HATZ> (raw)
In-Reply-To: <1726435.PWpjjHmTz1@omega>
On Sun, Dec 29, at 10:19 Bruno Haible wrote:
> Aga wrote:
> > - the returned value of the *printf family of functions dictates their
> > limits/range, as they return an int, this can be as INT_MAX mostly
>
> Yes, we need new implementations of the *asprintf functions that are not
> limited to returning strings of maximum length INT_MAX.
There is also the question how current functions behave with buffers over INT_MAX.
And what to do with such large buffers if stdio can not handle them reliably.
And what POSIX says about this if says at all?
next prev parent reply other threads:[~2019-12-29 20:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 13:45 hard-locale: make multithread-safe Bruno Haible
2019-12-17 14:08 ` Tim Rühsen
[not found] ` <20191226221225.GA800@HATZ>
2019-12-27 10:51 ` string types Bruno Haible
2019-12-28 13:14 ` ag
2019-12-28 18:28 ` Paul Eggert
2019-12-28 20:44 ` ag
2019-12-28 22:40 ` Paul Eggert
2019-12-29 9:19 ` Bruno Haible
2019-12-29 17:13 ` ag
2019-12-29 20:02 ` ag [this message]
2019-12-29 21:24 ` Tim Rühsen
2019-12-31 9:53 ` Bruno Haible
2020-01-06 10:34 ` Tim Rühsen
2020-01-06 12:46 ` Bruno Haible
2020-01-06 16:08 ` Tim Rühsen
2020-01-06 16:49 ` Tim Rühsen
2019-12-18 1:45 ` hard-locale: make multithread-safe Paul Eggert
2019-12-18 8:51 ` Bruno Haible
2019-12-21 6:33 ` Bruno Haible
2019-12-18 10:29 ` LC_COLLATE in the C locale Bruno Haible
2019-12-18 16:27 ` Paul Eggert
2019-12-18 10:46 ` hard-locale: make multithread-safe Bruno Haible
2019-12-24 23:36 ` Bruno Haible
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://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191229200226.GA13246@HATZ \
--to=aga.chatzimanikas@gmail.com \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=tim.ruehsen@gmx.de \
/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).