Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!orstcs!ogicse!zephyr.ens.tek.com!tektronix!nosun!qiclab!m2xenix!puddle!f101.n273.z1.fidonet.org!Peter.M..Perchansky
From: Peter.M..Perchansky@f101.n273.z1.fidonet.org (Peter M. Perchansky)
Newsgroups: comp.lang.modula2
Subject: Re: JPI M2 2.00 - PROCEDURE FUNCTIONS & ERROR CHECKING
Message-ID: <2302.26AF3E2B@puddle.fidonet.org>
Date: 25 Jul 90 14:44:49 GMT
Sender: ufgate@puddle.fidonet.org (newsout1.26)
Organization: FidoNet node 1:273/101 - Schizophrenia, Fleetwood PA
Lines: 13

Hello:

    Chris at JPI stated that the developers moved flow-traced errors such as having no return statement in a procedure defined as having a return to run-time error checking because they did not have enough time to make it a comple-time error.

    I am surprised Quick MOD did not catch this error at compile time. I though Stony Brook's compiler was superior to most DOS compilers.

    Almost all C compilers following the ANSI standard will catch the error I mentioned at compile time.



--  
uucp: uunet!m2xenix!puddle!273!101!Peter.M..Perchansky
Internet: Peter.M..Perchansky@f101.n273.z1.fidonet.org