Exaclly, especially since Algol 60 was one of the three languages folded into PL/I.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [[email protected]] on behalf of David Spiegel [[email protected]] Sent: Sunday, March 27, 2022 11:38 PM To: [email protected] Subject: Re: PL/I question Hi R'Shmuel AMV"SH, Like ALGOL and Pascal? Regards, David On 2022-03-27 22:52, Seymour J Metz wrote: > Personally, I wish that IBM had chosen ":=" for assignment. > > > -- > Shmuel (Seymour J.) Metz > https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmason.gmu.edu%2F~smetz3&data=04%7C01%7Csmetz3%40gmu.edu%7Ce9e248bf75944683e28408da106c86f3%7C9e857255df574c47a0c00546460380cb%7C0%7C0%7C637840355848465546%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=T0nyZXeRmQFRih61UBfLB4%2B%2FnKYUzInw%2BLudixXVtzs%3D&reserved=0 > > ________________________________________ > From: IBM Mainframe Discussion List [[email protected]] on behalf of > Rupert Reynolds [[email protected]] > Sent: Sunday, March 27, 2022 4:02 PM > To: [email protected] > Subject: Re: PL/I question > > Interesting. Thanks. > > I ask because many modern languages owe enough to C, or use libraries that > do, that it's become a working assumption that null, backslash and the like > will probably break something. > > I wrote a crude x86 compiler once, just to have a compiled language for my > own use that absolutely, definitely handled any byte value exactly the > same. It was supposed to be terse like C, but work more like PL/I. > > Oh, and I can't remember how far I got, but I started by abolishing = for > assignment. It was implicit in the syntax and = was only used for > comparison. I was young and foolish :-) > > Roops > > On Sun., Mar. 27, 2022, 18:10 Seymour J Metz, <[email protected]> wrote: > >> There are no troublesome characters. If it's CHARZ then a '00'X marks the >> end of the string, as in C. Otherwise there is an explicit length that is >> the same regardless of what characters are in the string. The length may be >> determined at, e.g. compile time, block entry, or may be dynamic (VARYING). >> >> >> -- >> Shmuel (Seymour J.) Metz >> https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmason.gmu.edu%2F~smetz3&data=04%7C01%7Csmetz3%40gmu.edu%7Ce9e248bf75944683e28408da106c86f3%7C9e857255df574c47a0c00546460380cb%7C0%7C0%7C637840355848465546%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=T0nyZXeRmQFRih61UBfLB4%2B%2FnKYUzInw%2BLudixXVtzs%3D&reserved=0 >> >> ________________________________________ >> From: IBM Mainframe Discussion List [[email protected]] on behalf >> of Rupert Reynolds [[email protected]] >> Sent: Sunday, March 27, 2022 11:45 AM >> To: [email protected] >> Subject: Re: PL/I question >> >> Related: how does LE handle strings with embedded troublesome bytes such as >> x'00'? And is it different between PL/I and C? >> >> I am reading the PL/I Programming Guide, but it takes but I'm hoping there >> is an easy off-the-cuff answer. >> >> Most of my PL/I experience was before LE, you see. >> >> Roos >> >> >> > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > . ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
