There were probably COBOL to PL/1 converters and PL/1 to COBOL converters at one time. PL/1 has many capabilities that COBOL does not such as local variables and dynamic mempory allocation. PL/1 has no equivalent to the SEARCH ALL verb in COBOL. So there are some programs that would have no equivalent.
B :=A; is only equivalent to MOVE A TO B if A and B are elementary fields. If A or B is a group (structure in PL/I), the statements produce completely different results.
This type of questions keep creeping up every now and then. Why would anyone strive to find "equivalent" source code from two different languages? It's complete nonsense because if we could routinely do this, then why have more than one programming language?
COBOL and PL/I are different in their approach to data processing. Is there any benefit or use to finding "equivalent" code between them?
I see as many openings for ALGOL as PL/1. And if you know what ALGOL is you are a real old-timer. But PL/1 is still around. There was a company that produced a PC version for it. It is vastly superior to COBOL but could never breach COBOL's enormous installed base. You can do almost anything in PL/1 that you can do in Assembler.
Before Microsoft (yes, there was such a time), every computer manufacturer used to have a "native" language for its machine.
IBM had (still does have) PL/I. Tandem has TAL. Prime (RIP) had PL1/G (a stripped version of PL/I). And so on...
These languages are usually maximized to take advantage of the machine architecture. Because of this, these languages are not suitable for "alien" machines.
So, it is highly unfair to compare a "universal" language such as COBOL against a "local" language such as PL/I.
That's why I cringe everytime languages are willy nilly "compared" against each other. For what it's worth, "native" languages should not be compared against common languages. For one, "native" languages are designed for coding and maintaining the local operating system, although people like using them for common business applications also.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.