Re: Something like string-streams existing in "C"?

Em 12/20/2024 8:00 AM, Michael S escreveu:

On Thu, 19 Dec 2024 23:14:17 -0300
Thiago Adams <thiago.adams@gmail.com> wrote:
 

Em 12/19/2024 7:06 PM, Kaz Kylheku escreveu:

On 2024-12-19, Michael S <already5chosen@yahoo.com> wrote:

On Thu, 19 Dec 2024 19:47:28 -0000 (UTC)
Kaz Kylheku <643-408-1753@kylheku.com> wrote:
 

On 2024-12-19, BlueManedHawk <bluemanedhawk@invalid.invalid>
wrote:

The ‘asprintf’ subroutine is standardized by POSIX.1-2024,
meaning that you can use it now and blame somebody else if it
doesn't work. If you

>
Regardless of how it is made visible, you can detect it via a
compile test in a configure script, and provide your own if it
wasn't found:
>
#if !HAVE_ASPRINTF
>
int asprintf(char **out, const char *fmt, ...)
{
    ... // more or less trivial to implement using malloc, realloc
and vsprintf

>
Don't you mean, vsnprintf ?

>
That detail will become obvious when you try to implement it.
  

>
I did on implementation in 2020 (not using it)
>
http://thradams.com/vadsprintf.html
>

 You mean, you don't use asprintf() that you implemented?
That's understandable. The API is rather badly designed. Can be handy
in toy examples, less so in production software.
 

For my needs a string stream is better I am using this
https://github.com/thradams/cake/blob/main/src/osstream.c
Unfortunately it is not compatible with FILE*.

>
The standard should have a string stream compatible with FILE because
- differently of asprintf - if cannot be implemented separately.
>

 What level of compatibility?
IMHO, the level that makes sense is where compatibility excludes
fopen, fclose and fflush. I.e. you have new functions, mem_fopen()
and mem_fclose() and do not allow fflush(). Pluse, you add few more
functions or macros for direct access to buffer.
 

A function printing in a FILE* fprint also should be able to print in a string stream.