My own memory is similar - Pascal was just generally annoying to use, in various little ways, that added up over time. On the face of it, it seems like it should be a lot better than C, but in practice... it just wasn't.
My own memory is similar - Pascal was just generally annoying to use, in various little ways, that added up over time. On the face of it, it seems like it should be a lot better than C, but in practice... it just wasn't.
No closures, so global vars everywhere
No breaks in flow control, it's goto (deprecated) or nothing
Strongly typed, but arrays of different lengths are different types.
Casting types is not possible
A number of annoying order-of-code requirements
"and" and "or" have no guaranteed precedence or order of operation..(!)
Those are enough to make me want to hurl the compiler against a wall.
> No breaks in flow control, it's goto (deprecated) or nothing
> Strongly typed, but arrays of different lengths are different types.
> Casting types is not possible
Those are real frustrations, but, at the same time, they help avoid many of the security and safety issues that have plagued C for decades.It's not clear if there's a language somewhere between Pascal that's less annoying but more safe while still being simple. But I think it is pretty clear that there is a real trade-off in either direction.
C doesn't get in your way when you know you're doing like Pascal does. But it also doesn't get in the way when you don't know what you're doing.
Flow control is significantly better, and supports goto style semantics when you need them.
Casting is liberally warned against (unsafe.*), but available when needed.
I think when an essay from 20 (or 35) years ago claiming "X sucks" is referenced, it's kinda foolish not to draw attention to the history that followed.