Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!purdue!i.cc.purdue.edu!h.cc.purdue.edu!s.cc.purdue.edu!ags
From: ags@s.cc.purdue.edu (Dave Seaman)
Newsgroups: comp.lang.pascal
Subject: Re: Control variables in FOR loops
Message-ID: <3693@s.cc.purdue.edu>
Date: 27 Dec 88 14:44:13 GMT
References: <1439@csuna.UUCP> <45@csd4.milw.wisc.edu> <1771@buengc.BU.EDU>
Reply-To: ags@s.cc.purdue.edu (Dave Seaman)
Organization: Purdue University
Lines: 13

In article <1771@buengc.BU.EDU> art@buengc.bu.edu (A. R. Thompson) writes:
>Ah, but since you've already established that it's an illegal program you
>can no longer predict what will happen.  That's strictly up to the
>compiler writer (who is duty bound to report the error and refuse to
>generate executable code).  

Not so.  The compiler writer is free to do whatever he likes, provided the
accompanying documentation describes the types of errors that are not
reported by the compiler.

-- 
Dave Seaman	  					
ags@j.cc.purdue.edu