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

On Mon, 24 Mar 2025 16:49:35 +0000
bart <bc@freeuk.com> wibbled:

On 24/03/2025 16:17, Muttley@DastardlyHQ.org wrote:

*GASP*! 12 whole seconds! How can you cope with your day being interrupted
like that for so long!

>
So applying your 100:1 ratio, you'd spend 20 whole minutes pondering
your next move before compiling again?

No, because unlike you I understand the concept of splitting into modules
and having a makefile that just rebuilds whats changed, not the entire
codebase.

When you have near-instant build times then it's completely different
way of working.

No it isn't. THat example I gave you built in 0.8 seconds. It would make
zero difference to me if it took 8 or 80.

Do you think people who work with scripting languages (or even writing
HTML) would tolerate an exasperating 12-second day between hitting Run,
and their test-run starting?

In the case of Python they tolerate hopeless performance so who knows.

In the case of this project, development is incremental: run a test,
there's an opcode not yet done, add the lines for it, test it again.
>
Or do a timing test, measure, tweak a line to two, time it again to see
if it's any better.
>
Or there might be bunch of configuration and debug settings, that don't
warrant dedicated CLI options, so to change a setting means changing one
line and rebuilding. Why not? It only takes an instant!
>
If I had to wait 10+ seconds each time then it would both take all
fucking day AND drive me around the bend.

See above for modules.

You really haven't got a clue.

Says the guy who rebuilds everything from scratch each time. Must be irony
week again.