Path: utzoo!utgpu!watmath!att!cbnews!r4
From: r4@cbnews.ATT.COM (richard.r.grady..jr)
Newsgroups: comp.lang.c
Subject: Re: want to know
Message-ID: <9055@cbnews.ATT.COM>
Date: 17 Aug 89 19:47:07 GMT
References: <8487@bsu-cs.bsu.edu> <2980@solo9.cs.vu.nl> <182@sunquest.UUCP> <14269@haddock.ima.isc.com> <1496@l.cc.purdue.edu> <31668@ism780c.isc.com>
Reply-To: r_r_grady@ATT.COM (richard.r.grady..jr)
Organization: AT&T Bell Laboratories
Lines: 31

In article <31668@ism780c.isc.com> marv@ism780.UUCP (Marvin Rubenstein) writes:
>In article <1496@l.cc.purdue.edu> cik@l.cc.purdue.edu (Herman Rubin) writes:
>>
>>Those who remember the old Fortran will know that one normally had a PROGRAM
>>card, which was of the form
>>
>>	PROGRAM NAME(.............)
>>
>
>Herman's recolection of old FORTRAN is different from mine.  The original
>FORTRAN (for the IBM 704) had no user written subroutine facility at all so
>the question of a name was moot.  FORTRAN/2, FORTRAN/4, (and I think
>FORTRAN/66) programs all begin execution with the one and only ANONYMOUS
 ^^^^^^^^^^
>program unit.  [...]

This is getting a bit away from the C language, but...

Control Data's version of FORTRAN/66 *required* a PROGRAM statement.
Furthermore, all I/O files (even standard input and output) had to be
declared in the PROGRAM statement.

          PROGRAM FOO(INPUT,OUTPUT,TAPE1,TAPE2,....)

where TAPE1, TAPE2, etc., corresponded to logical unit 1, 2, etc.
If you didn't declare a file this way, the program would barf.
(If you forgot OUTPUT, the barf was silent, because the complaint
routine couldn't find the file OUTPUT to write on!)

-------------------------------------------------------------------
Dick Grady              r_r_grady@att.com          ...!att!mvuxd!r4