Unfortunately Pascal got shot in the foot & not just by itself. When I was in higher education we got stuck with a syllabus which required us to use some mainframe "template". You couldn't just type in Pascal in an editor, it had to be "pre-parsed" and entered in sections in the way of prompts which could have only have been invented by some crazed cobol programmer.Heater wrote:Problem is there is no such thing as BASIC.
There are many languages that carry that name and are somehow similar. But they are all incompatible. There is no coherent standard.
Similarly for Pascal.
I want any code I write to be available in as many places as possible. Even if nobody else uses it, it future proofs it against changes in hardware, operating systems etc.
That means I need standards that everybody strives to support.
It was tolerable at first, reading characters to make up a string but thereafter a nightmare. It wouldn't allow the (non standard) string input facility and because you couldn't cut 'n' paste your working "string input function" into it - a real drudge. Sensible people skipped lectures to learn (back then K&R) C.
Then came Delphi. That's pretty cool but Borland struggled to expand the market, hence C++ Builder. It was a bit of a bodge but ultimately what killed it, was windows (imo). The RAD tool seemed great on the surface but a client would ask for seemingly trivial feature. Next thing you know, you're buried inside the winapi fighting it and the VCL.
My biggest regret (in programming terms) was not learning QT.