Hot answers tagged

7

It's important to keep in mind, that there weren't that much symbols using overstrike in basic (IBM) APL. By using an 8 bit codeset they all could be integrated. The most common charset on the mainframe side was Page 293 which extends EBCDIC with all (at that time) legal APL codes. With APL2 code handling became more complicated and Page 293 was replaced by ...


4

IBM had several different APL mainframe implementations, and they where updated and modified over many years to support different types of hardware and I/O equipment over their life time. The source for one of the earliest APL implementations for System/360 is available from the Computer History Museum. As far as I can remember they assign unique codes to ...


4

I was once writing an APL compiler (never finished, having figured I could single-handedly write a compiler in a 10 week undergraduate programming project), and the choice I made was to have an internal 8-bit character set where each composite symbol was a single character. This seemed an obvious choice to me, since that way you're separated from how that ...


3

Some 3270 terminals supported an optional Programmed Symbols feature, allowing the use of arbitrary character bitmaps. This was available on the 3279 Color Display Station (models 2B and 3B), the 3278 Display Station (models 2, 3 and 4) and the 3270 PC (with the Programmed Symbols card).


3

It's important to keep in mind, that there weren't that much symbols using overstrike in basic (IBM) APL. By using an 8 bit codeset they all could be integrated. The most common charset was Page 293 which extends EBCDIC with all legal APL codes. Symbols that get generated per overstrike, like log (⍟ which is 'Power-Overstrike' or PO), got their own code ...


Only top voted, non community-wiki answers of a minimum length are eligible