Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!zephyr.ens.tek.com!tektronix!nosun!qiclab!m2xenix!puddle!p4610.f46.n295.z2.fidonet.org!Dominique.Willems
From: Dominique.Willems@p4610.f46.n295.z2.fidonet.org (Dominique Willems)
Newsgroups: comp.lang.modula2
Subject: JPI M2 2.00 - PROCEDURE FUNCTIONS & ERROR CHECKING
Message-ID: <2411.26B332AC@puddle.fidonet.org>
Date: 26 Jul 90 09:18:00 GMT
Sender: ufgate@puddle.fidonet.org (newsout1.26)
Organization: FidoNet node 2:295/46.4610 - Starline System, Brussels Belgium
Lines: 26

Hi Peter,

I have JPI M2 V2.0, as probably you had already guessed...

 >       3)   What is your preference and why?

Quite an intriguing dilemma. Especially since it's further complicated by 
the result_optional switch in the Call pragma.
I'd say add another pragma giving you the choice; run-time, compile-time or 
no checking at all, defaulting to compile-time.

Since we already entered the world of more relaxed form-checking, like 
variable numbers of parameters and optional returns, I don't think another 
"philosophy-breaking" pragma can do any harm. If you're really a hard-core 
"no-compromises" Modula programmer, you can just leave all the pragmas alone 
and default to the standard.

What do you think ?

Regards,
Dominique


--  
uucp: uunet!m2xenix!puddle!2!295!46.4610!Dominique.Willems
Internet: Dominique.Willems@p4610.f46.n295.z2.fidonet.org