5 ms·
Also z/OS (formerly known as MVS) -large chunks of it are written in an IBM-internal-use-only PL/I dialect called PL/X. The core of the AS/400 operating system
by skissane 5y ago
Also z/OS (formerly known as MVS) -large chunks of it are written in an IBM-internal-use-only PL/I dialect called PL/X.
The core of the AS/400 operating system, OS/400, the Licensed Internal Code (LIC), used to be written in another IBM-only PL/I dialect, PL/MP. In, the 1990s, while porting the AS/400 from CISC to RISC, they rewrote all the PL/MP code into C++. But IBM has another private dialect of PL/I called PL/MI, which was used to write the higher level part of OS/400, the XPF - basically PL/MI compiled to the virtual machine bytecode but PL/MP compiled to the machine code of the physical hardware. From what I understand, parts of the XPF are still written in PL/MP even in the latest versions of OS/400 (now called IBM i OS), although newer components tend to be developed in C/C++ instead. Other parts of the XPF were written in Modula 2, and I believe there is still some Modula 2 code surviving in the most recent versions as well.
IBM has had even more secret proprietary PL/I variants. The long defunct IBM 8100 line’s DPPX operating system was a written in PL/DS. Another dialect, PL.8, used to be used to write IBM’s compilers (although I believe it has now been replaced by C++) and also some of the firmware for the mainframes. IBM even wrote a GCC front-end for PL.8, although it appears they never released it.
- the_only_law 5y agoI actually don’t mind PL/I. Always wondered one they needed a ton of derivative proprietary languages. I think I’d almost prefer language bloat.
- zozbot234 5y agoPL/I is a kitchen sink language already. Modern languages tend to minimize the amount of features that they provide in the language itself, and do as much as possible in their standard libraries. (This also goes together with simplified syntax, because user-defined complex syntax is hard, slow and potentially ambiguous, whereas limiting verbose, "readable" syntax to just a handful of language-provided features is just silly.)
- nobody9999 5y ago>PL/I is a kitchen sink language already. Speaking as someone who has delved into the intricacies of PL/I, I am sure that only Real Men could have written such a machine-hogging, cycle-grabbing, all-encompassing monster. Allocate an array and free the middle third? Sure! Why not? Multiply a character string times a bit string and assign the result to a float decimal? Go ahead! Free a controlled variable procedure parameter and reallocate it before passing it back? Overlay three different types of variable on the same memory location? Anything you say! Write a recursive macro? Well, no, but Real Men use rescan. How could a language so obviously designed and written by Real Men not be intended for Real Man use? Heh. Heh. Heh. [Source: http://www.anvari.org/fortune/Miscellaneous_Collections/362036_speaking-as-someone-who-has-delved-into-the-intricacies-of-pl-i-i-am-sure-that-only-real-men-could-have-written-such-a-machine-hogging-cycle-grabbing-all-encompassing-monster.html http://www.anvari.org/fortune/Miscellaneous_Collections/3620... ]
- Koshkin 5y agoLooks like a perfect language to write an OS in!
- gumby 5y agoMultics was written in PL/1
- the_only_law 5y agoAnd is still being updated!
- gumby 5y agoI should have written is, not was.
- kps 5y agoThe design criteria are as follows: 1. Anything goes. If a particular combination of symbols has a reasonably sensible meaning, that meaning will be made official. https://dl.acm.org/doi/10.1145/363707.363708 https://dl.acm.org/doi/10.1145/363707.363708
- shakna 5y ago> IBM even wrote a GCC front-end for PL.8, although it appears they never released it. Oh, how I had hoped I had scrubbed PL.8 from my memory. "80% of PL/I." Only missing everything that made it bearable to use PL/I. No interrupts. You get ITERATE but no LEAVE statement. No STATIC, EXPORT or PACKAGE. You do get DEFINE... But not the one in other IBM PL/? langs. Incompatible. The two weeks I spent debugging an interbank transferring program IBM wrote for them decades ago was one of the least pleasant experiences I've had when actually having access to the source code (albeit printed on five reams of paper, rather than digital). Give me pre-standard COBOL or FORTRAN over PL.8, any day. Though, to be fair, the version of PL.8 I was granted access to was the original compiler, only. Not the updated one used for z/Arch firmware, today. Which I think solves a lot of those things. And I do mean the original compiler. The very, very first version. I said no interrupts? Most of IBM's PL/? langs will signal when they run out of memory, so you can do something intelligent to kick the never-allowed-to-go-down mainframe into gracefully continuing to crunch endlessly (like clearing up part of a queue, and re-requesting it from a previous point). That signal is missing. So instead, you have developers build their own systems of heuristics to guess if a memory allocation had failed. Heuristics that had begun to fail, after an old network card burned out and was replaced with a similar one... But a faster, more modern, one. Faster hardware is the bane of old, hard-coded software. DCL IntVar INTEGER BASED (Cursed)
- skissane 5y ago> The two weeks I spent debugging an interbank transferring program IBM wrote for them decades ago was one of the least pleasant experiences I've had when actually having access to the source code (albeit printed on five reams of paper, rather than digital). Give me pre-standard COBOL or FORTRAN over PL.8, any day. Interesting. I didn't realise PL.8 was used to write application software. I knew about it being used to write compilers, firmware, etc. If customer applications were written in it, did this mean they actually shipped PL.8 development tools to customers? I thought it was always IBM-internal-only.
- shakna 5y ago> If customer applications were written in it, did this mean they actually shipped PL.8 development tools to customers? Access to the compiler was by special request, as was the source code for the project. It wasn't something generally available, but for this specific project, and there was someone whose job it was to make certain I didn't copy anything or so on. I have no reason to believe the interbank software was normal for IBM in any way, shape or form. I do have a suspicion as to why PL.8 was used instead of another language, and it does make a little bit of sense, but I'm afraid I don't believe that I'm currently allowed to reveal that. I've given what details I currently can.
- wglb 5y agoHere is a trivia question for you. What language was the first optimizing compiler written in?
- Tao331 5y agoIIRC this is the punchline of a story about Seymour Cray programming a BIOS in octal via front switches and blinkenlights. Or somewhere in that ballpark. It's a person, so the answer is DNA.
- pinewurst 5y agoIt was the initial IBM FORTRAN written in 704 assembler. Very much an optimizing compiler.
- wglb 5y agoNot quite. The idea of "basic blocks", key to optimizing compiler, was invented by the team that wrote the Fortran I compiler in Fortran I. See https://ucla-biostat-257-2020spring.github.io/readings/fortran.pdf https://ucla-biostat-257-2020spring.github.io/readings/fortr...
- rst 5y agoThe first Fortran I compiler is the one pinewurst was referring to, and it was written for the 704 -- in 704 assembly. Source code is here -- this is Fortran II (basically Fortran I plus provision for separately compiled subprograms), but obviously still assembly: http://www.softwarepreservation.org/projects/FORTRAN/index.html#Source_code http://www.softwarepreservation.org/projects/FORTRAN/index.h... (The article in the course reading you cited also correctly states that the compiler was written in assembly, for the 704.)
- deepspace 5y agoSpeaking of PL/I, Intel made a few operating systems in the late 70s / early 80s written in their dialect of PL/I called PL/M. There was ISIS, which ran on their microprocessor development stations, and iRMX, the real time O/S running on the target microprocessors. Having used both, ISIS was quite a bit more advanced than 'competitors' like DOS and CP/M at the time.
- skissane 5y ago> Speaking of PL/I, Intel made a few operating systems in the late 70s / early 80s written in their dialect of PL/I called PL/M PL/M was created by Gary Kildall, creator of CP/M, and CP/M 1.x was written in PL/M. In CP/M-80 2.x, they rewrote the kernel (BDOS) and command processor (CCP) in 8080 assembly to improve performance, but utility programs were still written in PL/M. Some later CP/M ports, such as CP/M-68K and CP/M-8000, were written in C instead. Wikipedia says that IBM used PL/M too – to write some of the firmware for the CISC AS/400s (the Service Processor).
- kragen 5y agoI think those might be two different PL/Ms that were both born in the 01970s.
- skissane 5y agoThey are the same PL/M. Gary Kildall was working at Intel as a contractor when he invented the first version of PL/M. Intel adopted it for their own internal software development (ISIS, RMX, etc), Kildall used it for writing CP/M and other Digital Research products. The compiler was forked into two versions – an Intel version and a Digital Research version – and they were mostly compatible, but each had some extensions the other lacked. As a result, code written for one couldn't always be compiled by the other.
- kragen 5y agoSorry, I was thinking of IBM's PL/M, which clearly wasn't the one Intel was using. Thanks for the correction.
- kragen 5y agoLast I heard DB2 was still written in PL/M too.
- skissane 5y agoDB2 is really four different products marketed under one brand – three of which have some PL/I heritage, the fourth doesn't: (1) DB2 for VM/VSE – the first to be released, as SQL/DS in 1981, its code was descended from IBM Research's System R research project, although most of that code was rewritten in the process of productisation (2) DB2 for z/OS – the first to be called "DB2" (the others were later rebranded to that), released for MVS in 1983. I believe this started life as a fork of the SQL/DS code base, but then evolved in a different direction (3) DB2 for IBM i – System/38 had an integrated database, but it was non-relational. In the process of evolving System/38 into the AS/400, IBM took the SQL layer out of SQL/DS (which was written in PL/S) and ported it to OS/400 (on which it would have been PL/MI code not PL/S, although those languages are very close to each other), but the lower layers of the stack (storage, etc) were kept from the System/38 non-relational database. In 1994, this was rebranded to "DB2/400", and more recently "DB2 for IBM i" (4) DB2 for Linux/Unix/Windows (LUW) – this began life as OS/2 Extended Edition Database Manager. It was written in C/C++ from the very start, it has never contained any PL/I dialect code, although some ideas/concepts/etc were borrowed from IBM's mainframe/midrange RDBMS products. The code base was ported from its OS/2 birthplace to Unix (including AIX, Solaris and HP/UX), Windows NT, and Linux. From what I understand (2) is still predominantly PL/X, although I would not be surprised if it now had some components in other languages such as C++. (1) is almost certainly mostly PL/X as well. (3) probably still contains PL/I-ish code too (albeit technically PL/MI rather than PL/X.) (Disclaimer: I have no firsthand knowledge of this – I was born around the time SQL/DS and DB2 for MVS was first released, and I've never worked for IBM. It is just what I've pieced together from publicly available sources.)