Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Kaz Kylheku <643-408-1753@kylheku.com>
Newsgroups: comp.lang.c
Subject: Re: Suggested method for returning a string from a C program?
Date: Tue, 25 Mar 2025 16:16:23 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 27
Message-ID: <20250325091057.166@kylheku.com>
References: <vrd77d$3nvtf$2@dont-email.me> <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> <vrrs20$14vob$1@dont-email.me>
 <vrrvnh$176lu$1@dont-email.me> <vrs0j5$191gt$1@dont-email.me>
 <vrs2eu$176lu$2@dont-email.me> <vrs2r3$1b0ov$1@dont-email.me>
 <vrs7oi$1e2j7$1@dont-email.me> <vrtq62$2unrb$1@dont-email.me>
 <vru2t0$35frt$2@dont-email.me> <vrufju$3i02s$1@dont-email.me>
Injection-Date: Tue, 25 Mar 2025 17:16:24 +0100 (CET)
Injection-Info: dont-email.me; posting-host="d3381b38f55d771d9a1d3766a5267560";
	logging-data="3872721"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+hxVVlpbR6cv0w0Lovz0RIFiAqKtHKd5A="
User-Agent: slrn/pre1.0.4-9 (Linux)
Cancel-Lock: sha1:AGKjnXuoX/0+Fscgrd1NSvZ404w=
Bytes: 3057

On 2025-03-25, Muttley@DastardlyHQ.org <Muttley@DastardlyHQ.org> wrote:
> Listen sonny, in large projects in companies - ie not the toy code you work
> on in your bedroom - different people will have checked out seperate modules
> and be working on them at any one time.

Splitting into files does make a big difference with centralized version
control that requires you to maintain a lock on an object that you are
modifying.

It makes little difference with distributed versioning systems like git.

You can catenate 10 .c files into a single one, and it would be just
as easy to work on in parallel.

However, git still has the concept of a file being one object.
You can "git log" a single file, and that is very useful;
If the file is a combination of what should be ten files, then
it becomes less useful.

I'm not suggesting people should combine files; it's a bad idea for
multiple reasons. Just that you *can* pretty easily work concurrently on
large files unless you're using a very outdated version control system.

-- 
TXR Programming Language: http://nongnu.org/txr
Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal
Mastodon: @Kazinator@mstdn.ca