Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site sdccsu3.UUCP
Path: utzoo!linus!philabs!sdcsvax!sdccsu3!zz1sm
From: zz1sm@sdccsu3.UUCP (Shane)
Newsgroups: net.lang.pascal
Subject: Re: No error message for missing "end" statement.
Message-ID: <1033@sdccsu3.UUCP>
Date: Wed, 10-Aug-83 11:13:42 EDT
Article-I.D.: sdccsu3.1033
Posted: Wed Aug 10 11:13:42 1983
Date-Received: Tue, 16-Aug-83 00:07:38 EDT
References: <432@sdcrdcf.UUCP>
Organization: U.C. San Diego, Student System 3
Lines: 14

At UCSD, we use Berkeley Pascal in some of our upper-division EECS
courses. This bug quickly bared its teeth when students in a compiler
writing course started using seperate compilation of BPascal routines.
Of course, since the compiler doesn't generate a diagnostic, it is
frustrating to find, at the end of a big make, that you have to go
back and remake the whole thing. (Worse, the bug was usually not identified 
correctly by many students). Anyway, best way to get a diagnostic seems to
be to just insert an extraneous 'end' at the end of the file containing
the routine which the linker says is undefined at ld time. Then you 
will get a diagnostic that should properly inform you of the missing
end (which is now an improperly placed end).

Shane
ucbvax!sdcsvax!sdccsu3!zz1sm