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

On Mon, 24 Mar 2025 15:32:32 +0100
David Brown <david.brown@hesbynett.no> wibbled:

On 24/03/2025 15:07, bart wrote: 

What was strange was that that one view was shared by pretty much
everyone in comp.lang.c. 

>
Do you know what the people in comp.lang.c have in common?
>
We program in C.
>
Do you know /why/ people program in C?
>
There can be many reasons, but a very common one is that they want
fast resulting binaries.  Most serious programmers are familiar with
more than one language, and pretty much all other languages are
higher level, easier, and have higher developer productivity than C
- but the resulting binaries are almost always slower.
>
C programmers are typically not bothered about build times because
a) their build times are rarely high (Scott's projects are C++), and
b), they are willing to sacrifice high build times if it means more
efficient run times. 

 
I'm not sure what kind of build time he's looking for either. On this
Mac ARM laptop I can compile a 7600 line utility I wrote in C in 0.8
seconds real time, and that is using a makefile with 18 seperate
source files and a header and includes link time. So unless he's
rebuilding the linux kernel every day I don't see what the problem is.
 
loki$ ls *.c *.h | wc -l
      19
loki$ wc -l *.c *.h
:
:
     691 globals.h
    7602 total
loki$ time make
:
:
real 0m0.815s
user 0m0.516s
sys 0m0.252s