| Related articles |
|---|
| From: | gah4 <gah4@u.washington.edu> |
| Newsgroups: | comp.compilers |
| Date: | Sun, 2 Oct 2022 00:11:53 -0700 (PDT) |
| Organization: | Compilers Central |
| References: | 22-09-026 22-10-002 22-10-004 |
| Injection-Info: | gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="11572"; mail-complaints-to="abuse@iecc.com" |
| Keywords: | PL/I, history |
| Posted-Date: | 02 Oct 2022 15:36:25 EDT |
| In-Reply-To: | 22-10-004 |
On Saturday, October 1, 2022 at 6:34:58 PM UTC-7, gah4 wrote:
(snip)
(our moderator wrote)
> [PL/I was a remarkably good language considering what a rush job it was but
> it has plenty of odd things, e.g.
> DCL (I, J, K) CHAR(3);
> I = 1;
> J = 2;
> K = I+J;
> What does K contain? Nope, it contains three spaces because the 1 and 2
> are converted to ' 1' and ' 2', they're converted back to integer,
> added, converted back to to a default size integer string
> like ' 3' and string assignment truncates from the right. -John]
Yes.
In the DO loop example, the first try was with K='100';
but the second had three blanks before the 100. That way the
string comparison works.
And the SQRT is done in double precision.
Return to the
comp.compilers page.
Search the
comp.compilers archives again.