Sujet : Re: Suggested method for returning a string from a C program?
De : Muttley (at) *nospam* DastardlyHQ.org
Groupes : comp.lang.cDate : 24. Mar 2025, 17:17:41
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vrs0j5$191gt$1@dont-email.me>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28
On Mon, 24 Mar 2025 16:02:57 +0000
bart <
bc@freeuk.com> wibbled:
On 24/03/2025 15:00, Muttley@DastardlyHQ.org wrote:
real 0m0.815s
user 0m0.516s
sys 0m0.252s
>
>
So, your throughput is a whopping 9.5K lines/second?
On a tired laptop with multiple files it seems pretty good to me.
Build time is 1/15th of a second, for about 30K lines (so 450Klps). But
I also want to compile this via C, to take advantage of gcc's superior
optimiser. So first I transpile to C (that's also under 70ms):
I'll paraphrase someone elses point - who fucking cares? If you need lightning
fast compilation because you're constantly rebuilding your shit code to see if
it'll even compile never mind work then that says a lot about you as a dev.
The thinking/writing to compilation time ratio I imagine with most devs would
probably be a minimum of 100 - 1, possibly much larger.
The generated C file is 38Kloc, and takes 12 seconds. It takes nearly
TWO HUNDRED TIMES longer to build.
*GASP*! 12 whole seconds! How can you cope with your day being interrupted
like that for so long!
I can tolerate that from time to time,
Get a life.