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 > http://mason.gmu.edu/~smetz3 > > ________________________________________ > 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
