>>11800547that language is an absolute crock of shit. decent to learn the basics of imperative programming, terrible for everything else. it's a very simple and base language and foundation for many imperative programming languages, but you are prone to mistakes that are both hard to spot and difficult to analyse without the proper IDE.
For example, i got into so many fucking troubles during one of my early exams on nested for cycles. as it turns out, when exiting the for cycle, the counter is updated anyway, but no one told me that, and neither did C. I spent 1.30h looking for a retarded mistake that the language doesn't tell you.
and what about arrays and pointers? if you lose the pointer to the original cell of the array you are entirely screwed. and if you dynamically allocate something and don't free it, your memory kisses you goodbye.
some versions of C don't even allow you to intermix declarations and code. if you need a temporary variable somewhere in a while cycle or whatever, C will flip you off.
you are prone to making hard to find and code-breaking errors, or things that are not even errors and are treated as such. Go for it if you are a beginner, but when you learn the basics switch to functional
