Path: utzoo!attcan!uunet!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: <2608.26B7D090@puddle.fidonet.org>
Date: 30 Jul 90 14:57:45 GMT
Sender: ufgate@puddle.fidonet.org (newsout1.26)
Organization: FidoNet node 1:273/101 - Schizophrenia, Fleetwood PA
Lines: 11

Hello Dominque:

    What do I think?  I think the first form of defensive programming outside of the programmer is compile-time errors followed by run-time errors.

    What gets me is that JPI M2 1.17 issued a compile-time error, but JPI M2 2.00 issues a run-time error; bad switch in my opinion.



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