Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!cbatt!cbosgd!ihnp4!inuxc!pur-ee!uiucdcs!ccvaxa!aglew
From: aglew@ccvaxa.UUCP
Newsgroups: net.lang
Subject: Re: Re: nested procedures.
Message-ID: <800021@ccvaxa>
Date: Sun, 17-Aug-86 16:55:00 EDT
Article-I.D.: ccvaxa.800021
Posted: Sun Aug 17 16:55:00 1986
Date-Received: Tue, 19-Aug-86 04:32:38 EDT
References: <7026@boring>
Lines: 16
Nf-ID: #R:boring:-702600:ccvaxa:800021:000:815
Nf-From: ccvaxa.UUCP!aglew    Aug 17 15:55:00 1986


>    A procedure without procedure parameters can be asserted with 
>pre- and post-conditions. The inclusion of procedure parameters makes
>it almost impossible to assert the pre- and post-conditions. In other words
>procedures with procedure parameters are just control macros, not solid
>abstraction. 

Bullshit. You can provide pre and post conditions for a procedure only
because you are able to do so for each statement in the procedure. An
invocation of a procedure parameter can have valid procedure parameters
just as easily as any other parameter. These must be satisfied by
all procedures that can be passed to that parameter.

Unfortunately, satisfaction of these pre and post conditions is rarely
checked automatically for procedure parameters, but then, neither is it
done for complex data structures.