Re: Suggested method for returning a string from a C program?

On 3/22/2025 6:06 AM, bart wrote:

On 22/03/2025 03:50, Keith Thompson wrote:

bart <bc@freeuk.com> writes:

On 21/03/2025 19:04, Keith Thompson wrote:

bart <bc@freeuk.com> writes:

On 21/03/2025 01:47, Keith Thompson wrote:

bart <bc@freeuk.com> writes:
You're complaining about how much work it is.  All that work
has been done for you by the implementers.  Decades ago.

>
We are talking about defining types like 'int32' on top of 'char short
int long', yes? Then how difficult could it possibly be?

If you want <stdint.h> and <inttypes.h> headers that work correctly
with all relevant compilers, it's not particularly easy.  I'll note
that the MUSL implementation of <stdint.h> is 117 lines, compared to
308 for GNU libc.
>

I just did a quick test comparing complation times for an empty
program with no #include directives and an empty program with
#include directives for <stdint.h> and <inttypes.h>.  The
difference was about 3 milliseconds.  I quite literally could not
care care less.

>
I'm sorry but that's a really poor attitude, with bad
consequences. You're saying it doesn't matter how complex a header or
set of headers is, even when out of proportion to the task.
>
But this is why we end up with such complicated headers.

Complicated headers that work.
[...\
>

I think your response clarifies matters. Nobody cares, even as
compilers grind to a halt under all preprocessing.

If compilers ground to a halt, I would certainly care.  They don't.

>
50 modules each including GTK.h say, which was 0.33Mloc across 500
headers (so reading 16Mloc and 25,000 headers in total when all are
compiled) would not impact your builds at all? OK.

>
First you talked about compilers grinding to a halt, then you talked
about headers not impacting builds at all.  Those goalposts of yours
move *fast*.

 You missed the "?".
 

For the record, as you can see above, I did not say that builds would
not be impacted.  Do not put words into my mouth again.

 Let me ask it again: so ploughing through a third of a million lines of code across hundreds of #includes, even at the faster throughput compared with compiling code, for a module of a few hundred lines, will have little impact?
 How about a project with 50 or 100 modules, each using that big header, that needs to be built from scratch?

For some reason you are making me think of pre-compiled headers. Ever include <windows.h> even with WIN32_LEAN_AND_MEAN? ;^)
Not even sure of this is in context, but you make be think of PCH.
Sorry. ;^o
[...]