Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!henry From: henry@utzoo.UUCP (Henry Spencer) Newsgroups: net.lang.c Subject: Re: Multilevel standards Message-ID: <4882@utzoo.UUCP> Date: Tue, 8-Jan-85 11:28:16 EST Article-I.D.: utzoo.4882 Posted: Tue Jan 8 11:28:16 1985 Date-Received: Tue, 8-Jan-85 11:28:16 EST References: <4859@utzoo.UUCP>, <11@mit-athena.ARPA> Organization: U of Toronto Zoology Lines: 17 > > The problem with Pascal was that the original language was excessively > > minimal. We *have* avoided this trap with C, since it was in heavy use > > for production work long before K&R, much less the current ANSI effort. > > Hey, c/mon fellas! Pascal was designed as an introductory language for > a first programming course. Of course, it's restricted! A full system > language (like C) is not appropriate for Programming 101. A toy language > (like Pascal) is not appropriate for building operating systems. I'm not heaping scorn on Pascal; I was a founding member of the Pascal Users Group. (Literally: I was at the little meeting at ACM 75 that started the group.) But Pascal's problems are not restricted to cases where it is being misapplied. How can one teach defensive programming without an OTHERWISE in the CASE statement??? Oh well... -- Henry Spencer @ U of Toronto Zoology {allegra,ihnp4,linus,decvax}!utzoo!henry