51 ms·
I don’t think cobol is that difficult; the problem is that it runs on the mainframe, and that’s a whole different beast. Everything in the mainframe world is bo
by setr 3y ago
I don’t think cobol is that difficult; the problem is that it runs on the mainframe, and that’s a whole different beast. Everything in the mainframe world is both expensive and vendor-supplied, so it’s difficult to learn outside the company, and sufficiently proprietary that you’re probably not going to transfer it well elsewhere.
The language itself also encourages troublesome patterns, like all variables essentially being globally defined and untyped, procedure line numbers matter because of things like PERFORM A THROUGH B (which will execute all logic found between paragraph A and paragraph B)
- jacquesm 3y agoPERFORM PERFORM UNTIL ... The reason for that is that originally the 'WITH TEST BEFORE' bit wasn't there so what looked like the test was done afterwards actually would just exit the loop immediately without executing the loop body at all. So the syntax totally wrong-footed you into believing that your loop body would always be executed at least once but never did...