[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: string types
From: |
ag |
Subject: |
Re: string types |
Date: |
Sun, 29 Dec 2019 22:02:26 +0200 |
User-agent: |
Mutt/1.12.1 (2019-06-15) |
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?
- hard-locale: make multithread-safe, Bruno Haible, 2019/12/17
- Re: hard-locale: make multithread-safe, Tim Rühsen, 2019/12/17
- Message not available
- Re: string types, Bruno Haible, 2019/12/27
- Re: string types, ag, 2019/12/28
- Re: string types, Paul Eggert, 2019/12/28
- Re: string types, ag, 2019/12/28
- Re: string types, Paul Eggert, 2019/12/28
- Re: string types, Bruno Haible, 2019/12/29
- Re: string types, ag, 2019/12/29
- Re: string types,
ag <=
- Re: string types, Tim Rühsen, 2019/12/29
- Re: string types, Bruno Haible, 2019/12/31
Re: hard-locale: make multithread-safe, Paul Eggert, 2019/12/17