non-standard const-preserving string APIs

[Alejandro Colomar]

Hi Florian,

On 2026-06-01T13:41:16+0200, Florian Weimer wrote:
> > I will try to take a look, but I recall from previous weekly calls
> > that Florian has raised objection that this does not solve the
> > overflow issue (not without further extra changes).
> 
> <https://inbox.sourceware.org/libc-alpha/lhums05zjuh.fsf@oldenburg.str.redhat.com/>
> 
> > I am not sure if he still keep his objection, nor if it is would a
> > blocker for this new api.
> 
> I still think we should fix it.  Maybe rename the “done” variable in the
> vfprintf internals to “ssize_t”, and then gradually fix the compilation
> failures, investigating whether the change is correct in context.  We
> need to add some early bailout in case INT_MAX is crossed for the
> non-aprintf case.

Would you mind at least confirming whether the current patches are OK
modulo the EOVERFLOW issue?  It's the first time I touch many of these
files (e.g., abilist files), and I'd appreciate if you reviewed it so
that I can forget about that part.


Have a lovely night!
Alex

> 
> Thanks,
> Florian
> 

-- 
<https://www.alejandro-colomar.es>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://sourceware.org/pipermail/libc-alpha/attachments/20260602/27aa132b/attachment-0001.sig>