[sdiy] Programming Language Recommendation

Spiros Makris spirosmakris92 at gmail.com
Mon Dec 7 19:29:11 CET 2020

You can include code in .h files. If you just need 200 lines of code for a
utility library or class there's no need for a .c file as far as I
If you divide your code in .h and .c files you can have an easier to handle
structure for your programme/library, as well as be able to easily change
the implementation of a given function without changing the rest of the
So it *is usually *avoidable in C as well, but I would argue it is
desirable, especially in larger programmes. I've had applications where a
single .h file was supplemented by 3-4 .c files, each containing the
functions that had some common functionality. Navigating 100-300 lines at a
time feels a lot less confusing than having to scroll through 1500 lines to
find what you need.

On Mon, Dec 7, 2020 at 6:50 PM Tom Wiltshire <tom at electricdruid.net> wrote:

> It’d be mine too if it wasn’t for the .h header files. They’re just
> irritating and means it usually takes two files to do the job of one file.
> No other language I’ve used felt the need to have such a thing, so I don’t
> see why it should somehow be unavoidable in C.
> On 7 Dec 2020, at 16:28, Michael E Caloroso <mec.forumreader at gmail.com>
> wrote:
> C is still my favorite language.
> _______________________________________________
> Synth-diy mailing list
> Synth-diy at synth-diy.org
> http://synth-diy.org/mailman/listinfo/synth-diy
> Selling or trading? Use marketplace at synth-diy.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://synth-diy.org/pipermail/synth-diy/attachments/20201207/627bf5a9/attachment.htm>

More information about the Synth-diy mailing list