←back to thread

Brent's Encapsulated C Programming Rules (2020)

(retroscience.net)
78 points p2detar | 1 comments | 09 Dec 25 11:16 UTC | HN request time: 0s | source
Show context
Jean-Papoulos ◴[09 Dec 25 12:20 UTC] No.46204131[source]▶
>What this means is that you can explain all the intent of your code through the header file and the developer who uses your lib/code never has to look at the actual implementations of the code.

I hate this. If my intellisense isn't providing sufficient info (generated from doc comments), then I need to go look at the implementation. This just adds burden.

Headers are unequivocally a bad design choice, and this is why most of every language past the nineties got rid of them.

replies(3): >>46204695 #>>46205042 #>>46205098 #
GhosT078 ◴[09 Dec 25 13:26 UTC] No.46204695[source]▶
Look to Ada for “headers” (i.e. specs) done right.
replies(1): >>46206504 #
1. runlaszlorun ◴[09 Dec 25 16:04 UTC] No.46206504[source]▶
Recently became big Ada fanboy, ironic because Im far more a fan of minimal, succinct syntax like lisp, forth, etc and I actually successfully lobbied a professor in 1993 to _not_ use it in an undergrad software engineering class lol.

Still in the honeymoon phase granted, but I'm actually terrified that we have these new defense tech startups have no clue about Ada collectively.

Your startup MVP you wants to ship a SaaS product ASAP and iterate? Sure, grab Python or JS and whatever shitstorm of libraries you want to wrestle with.

Want to play God and write code that kills?

Total category error.

The fact that I'm sure there are at least a few of these defense tech startups yolo'ing our future away with vibe coded commits when writing code that... let's not mince our words... takes human life... prob says about how far we've fallen from "engineering".