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

On 3/24/2025 8:42 AM, Scott Lurndal wrote:

bart <bc@freeuk.com> writes:

On 24/03/2025 11:51, David Brown wrote:

On 23/03/2025 02:34, bart wrote:
>

It's strange: in one part of the computing world, the speed of
building software is a very big deal. All sorts of efforts are going
on to deal with it. Compilation speed for developers is always an
issue. There is a general movement away from LLVM-based backends /
because/ it is so slow.
>
And yet in another part (namely comp.lang.c) it appears to be a total
non-issue!
>

>
You find it strange that different parts of the computing world (or,
more appropriately, software development world) have different
priorities, needs and focuses for their tools?  I find it very strange
that anyone would find that strange!
>
>

>
What was strange was that that one view was shared by pretty much
everyone in comp.lang.c.
>
Even though one or two (like Scott Lurndal) had reported significant
build times (even you had remarked on it and made suggestions), but that
was brushed off.

 You're taking my statements out of context.  Yes, a build for a
very large project (which you've never seen, much less worked on),
can take time.   That's just a fact.  Your tools could never build
such a project.

I don't know if they can or not. However, it might take his tools some time to build the whole beast, so to speak. It can be beneficial to separate out the large project into different parts such that part A only needs to be built, not parts B...Z, so to speak.

 

>
I don't know; maybe with fast builds, people would have to do more work
instead of taking a coffee break!

 Or they use tools like make(1) to increase productivity by only
rebuilding the portion of the project that needs to be rebuilt;
which takes a few seconds.  Thus, they already have fast builds
and aren't wasting cycles rebuilding code that hasn't changed.