Hacker News new | ask | show | jobs
by shannongreen 1807 days ago
As someone who has to write C for their day job, I am a little bit offended by the introduction of this article, but I guess that's the point.

The code presented is trash and doesn't follow best practices - using the type system, descriptive variable names, etc. Void pointers for everything, are you serious? Of course it's hard to understand. Revealing that it's the generated code doesn't make me any more comfortable with it.

Yes, I get that you shouldn't care what the generated code looks like if you trust your input, but I don't find the predicate any easier to understand. How do I know that's correct? What if I need to debug this generated output?

2 comments

I have seen code written like that by humans, namely offshored projects.
I've taken "Goodbye C developers" out of the title above, since it's pretty linkbaity.