Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site ncsu.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!decvax!mcnc!ncsu!mauney
From: mauney@ncsu.UUCP (Jon Mauney)
Newsgroups: net.lang.c
Subject: Re: Language transitions
Message-ID: <2793@ncsu.UUCP>
Date: Mon, 11-Feb-85 10:08:29 EST
Article-I.D.: ncsu.2793
Posted: Mon Feb 11 10:08:29 1985
Date-Received: Thu, 14-Feb-85 01:43:13 EST
References: <252@gumby.UUCP> <535@ukma.UUCP> <258@gumby.UUCP> <4475@ucbvax.ARPA>, <590@ncoast.UUCP>
Organization: N.C. State University, Raleigh
Lines: 15

> Pascal has two major problems:  (1) it was designed as a *teaching* language,
> and (2) it was designed for batch systems -- the "PROGRAM FOOBIE(INPUT,
> OUTPUT, BLETCH);" was intended to be linked to a file name via the CDC
> version of a "DD" statement.

Fortunately, C is clearly intended for interactive systems, and no-one
would ever see a connection between stdin/stdout and SYSIN/SYSOUT.

Of the many flaws in Pascal, ordinary I/O is not one.  There is nothing
preventing good interactive execution of Pascal programs.
-- 

*** REPLACE THIS LINE WITH YOUR SIGNATURE ***

Jon Mauney    mcnc!ncsu!mauney    C.S. Dept, North Carolina State University