home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!munnari.oz.au!goanna!ok
- From: ok@goanna.cs.rmit.oz.au (Richard A. O'Keefe)
- Newsgroups: comp.programming
- Subject: Re: Teaching the basics
- Message-ID: <14139@goanna.cs.rmit.oz.au>
- Date: 21 Aug 92 08:39:26 GMT
- References: <Bt6DGq.HuB@metropolis.com> <12635@anderson> <MHCOFFIN.92Aug20162507@tolstoy.uwaterloo.ca>
- Organization: Comp Sci, RMIT, Melbourne, Australia
- Lines: 20
-
- In article <MHCOFFIN.92Aug20162507@tolstoy.uwaterloo.ca>, mhcoffin@tolstoy.uwaterloo.ca (Michael Coffin) writes:
- > In article <13226@bnr-rsc.UUCP> sdms@bnr.ca (Andrew Sterian) writes:
- > > Hmmmm...I disagree on this one. It may have been true some years ago that
- > > the type checking etc. of Pascal made it easier on novice programmers but
- > > the latest ANSI C compilers do just as good a job of it as Pascal.
- >
- > I've heard this said with quite a bit of frequency lately, but it
- > isn't true. C compilers---even ANSI ones---don't do type
- > checking across separately compiled files.
-
- Pascal doesn't do type checking across separately compiled files either.
- (I'm not talking about "PAscal Extended" here; I still haven't seen that.)
- Suppose you want to write a program that calls procedure P, but you want
- to put P in another file. There is _no_ way to do that in standard Pascal.
-
- There is nothing in the C standard that _forbids_ type checking across
- separately compiled files, and there _are_ ANSI-compatible Lints. We've
- ordered one, but heaven only knows when we'll get it. In the mean time,
- --
- You can lie with statistics ... but not to a statistician.
-