From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=0.6 required=5.0 tests=BAYES_05,INVALID_DATE,
	MSGID_SHORT autolearn=no autolearn_force=no version=3.4.4
Path: utzoo!attcan!uunet!crdgw1!jupiter!kassover
From: kassover@jupiter.crd.ge.com (David Kassover)
Newsgroups: comp.lang.ada
Subject: Re: if UNIX then USE_C ?? (was: Reasons for drop)
Keywords: Functions and side effects
Message-ID: <5659@crdgw1.crd.ge.com>
Date: 1 Mar 90 18:29:38 GMT
References: <27187@cup.portal.com> <18175@megaron.cs.arizona.edu> <5563@crdgw1.crd.ge.com> <184@trwacs.UUCP> <5638@crdgw1.crd.ge.com> <6553@hydra.gatech.EDU>
Sender: news@crdgw1.crd.ge.com
Organization: Aule-Tek, Inc.
List-Id: <comp.lang.ada>

In article <6553@hydra.gatech.EDU> tynor@prism.gatech.EDU (Steve Tynor) writes:
>In article <5638@crdgw1.crd.ge.com> kassover@control.crd.ge.com (David Kassover) writes:
>>complex subprogram execution is called for.  What can screw you
>>up here is a "SIDE EFFECT", which Ada flatly refuses to allow.
>

It should be obvious by now that what I was referring to as a
SIDE EFFECT was the changing of the values of parameters of
functions, that is, a PARAMETER that gets changed incidentally to
the generation of the return value.  This is how I have always
understood the term to be meant, as mentioned in K&R and K&P.