Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Muttley@DastardlyHQ.org
Newsgroups: comp.lang.c
Subject: Re: Suggested method for returning a string from a C program?
Date: Mon, 24 Mar 2025 15:00:17 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 44
Message-ID: <vrrs20$14vob$1@dont-email.me>
References: <vrd77d$3nvtf$2@dont-email.me> <20250319115550.0000676f@yahoo.com>
 <vreuj1$1asii$4@dont-email.me> <vreve4$19klp$2@dont-email.me>
 <20250319201903.00005452@yahoo.com> <86r02roqdq.fsf@linuxsc.com>
 <vrh1br$35029$2@dont-email.me> <LRUCP.2$541.0@fx47.iad>
 <vrh71t$3be42$1@dont-email.me> <874izntt5t.fsf@nosuchdomain.example.com>
 <vrhviu$h5c$1@dont-email.me> <87ecyrs332.fsf@nosuchdomain.example.com>
 <vri9t1$a29t$1@dont-email.me> <20250320171505.221@kylheku.com>
 <vrif1v$c9ev$3@dont-email.me> <8734f7rw7z.fsf@nosuchdomain.example.com>
 <vrjjvb$1esjh$1@dont-email.me> <87tt7mqk7w.fsf@nosuchdomain.example.com>
 <vrkvt5$2k04q$2@dont-email.me> <87cye9afl0.fsf@nosuchdomain.example.com>
 <vrmckn$114k$1@dont-email.me> <871puoag2q.fsf@nosuchdomain.example.com>
 <vrnoft$15f6n$1@dont-email.me> <vrrh0c$qila$1@dont-email.me>
 <vrrouo$11up7$1@dont-email.me>
 <vrrqe0$12u8q$1@dont-email.me>
Injection-Date: Mon, 24 Mar 2025 16:00:17 +0100 (CET)
Injection-Info: dont-email.me; posting-host="b7e7a06d9975f4b3f6815cf483b65e42";
	logging-data="1212171"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+D1ixn8091Buh9HLOy3R8C"
Cancel-Lock: sha1:94rJ8puOEq9c6zOjdfJXVue/h7U=
Bytes: 3118

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