Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!wuarchive!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: <403.26C179B8@puddle.fidonet.org>
Date: 8 Aug 90 14:47:34 GMT
Sender: ufgate@puddle.fidonet.org (newsout1.26)
Organization: FidoNet node 1:273/101 - Schizophrenia, Fleetwood PA
Lines: 15

Hello Ernie:

    One of the main reasons why most Modula-2 implementations shines over other language implementations is Modula-2's strong typing.

    Most errors are caught during compilation (which takes only seconds or minutes) as opposed to during run-time (which can takes months of testing before poping up).

    JPI stated that they did not have enough time to implement a compile-time error for not having a return statement in a procedure (function) defined as having a return value in JPI M2 2.00 release 1.04.

    I recently received release 1.05b, and they still did not implement this feature - even though it is present in JPI M2 1.17.



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