PL/C (was: Wonder why IBM code quality is suffering?)

PL/C was an interesting compiler.

It provided the capability to correct many common coding errors.

Unfortunately, there was no guarantee that it would correct the coding error
in the way you might expect.

You could actually give PL/C no input. I would then detect the lack of a
"MAIN" procedure and would then build a dummy "MAIN" procedure.

John P Baker
Software Engineer

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@xxxxxxxxxxxx
Of Tom Schmidt
Sent: Sunday, March 26, 2006 23:12
To: IBM-MAIN@xxxxxxxxxxx
Subject: Re: Wonder why IBM code quality is suffering?

On Sun, 26 Mar 2006 19:33:18 -0500, Richard Tsujimoto wrote:

Jeez, (IIRC) I still remember it being PL/C.


No, PL/C was Cornell University's student PL/1 compiler.
(I remember it, too; Waterloo had it as one of their batch compilers, as
did ISU and many other colleges and universities around the world.)

The PL/X genealogy included PL/S and PL/AS, but not PL/C.

--
Tom Schmidt
Madison, WI

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to listserv@xxxxxxxxxxx with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to listserv@xxxxxxxxxxx with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
.

Relevant Pages

  • Re: MULTICS PL/I and PL/C
    ... Multics PL/I and PL/C present opposite problems. ... there were only a few copies to begin with: Cornell obviously, ... The Multics compiler at least has survived, ...
    (comp.lang.pl1)
  • Re: MULTICS PL/I and PL/C
    ... I've asked a friend at RPI, but they tossed all the mainframe stuff with the mainframe in 1999. ... PL/C did a lot of cheating. ... The Multics compiler at least has survived, ...
    (comp.lang.pl1)
  • Re: (long) An AES implementation for 32-bit platforms
    ... locate some coding errors of mine that had splipped ... Change 'void main' to 'int main'. ... compiler of DJGPP with the option -Wall in compilation. ...
    (sci.crypt)
  • Re: PL/I features
    ... For example, PL/C used reserved words. ... When reading someone else's PL/I ... Also, IIRC, PL/C did not support AREAs or OFFSETs. ... However, as CG suggests, neither compiler generated production-quality ...
    (comp.lang.pl1)
  • Re: #define and (brackets)
    ... coding errors. ... CRect rct; ... leads to a compiler error. ... handling tokens rather than individual characters. ...
    (microsoft.public.vc.language)
Loading