Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!caip!topaz!root
From: root@topaz.RUTGERS.EDU (Charles Hedrick)
Newsgroups: net.lang.c,net.lang.pascal
Subject: Re: Interactive I/O in Pascal
Message-ID: <5475@topaz.RUTGERS.EDU>
Date: Sat, 2-Aug-86 01:31:08 EDT
Article-I.D.: topaz.5475
Posted: Sat Aug  2 01:31:08 1986
Date-Received: Sat, 2-Aug-86 10:56:17 EDT
References: <2222@brl-smoke.ARPA> <7014@boring.mcvax.UUCP>
Organization: Rutgers Univ., New Brunswick, N.J.
Lines: 12
Xref: watmath net.lang.c:10135 net.lang.pascal:610

Because Pascal does strong type-checking, it would be hard to write
anything like printf and scanf for it.  Indeed if writeln and readln
were not built into the compiler, you would not be able to define them
yourself.  A Pascal procedure must have a fixed number of arguments,
each of a definite type.  Thus the best you could do would be
  printint(int i);
  printreal(real r);
etc.  Unfortunately, I/O libraries are not something that can be
tacked on later.  I/O affects the definition of the language.  This is
one of the most serious problems with the languges in the Algol
tradition.  There is a tendency to think I/O is a detail unfit for
computer scientists, which can be left to the "standard prolog".