From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 19674 invoked from network); 14 May 2020 12:25:57 -0000 Received: from minnie.tuhs.org (45.79.103.53) by inbox.vuxu.org with ESMTPUTF8; 14 May 2020 12:25:57 -0000 Received: by minnie.tuhs.org (Postfix, from userid 112) id B9CF29C66A; Thu, 14 May 2020 22:25:51 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id BAE1A9C669; Thu, 14 May 2020 22:25:23 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=fail reason="signature verification failed" (1024-bit key; secure) header.d=mxes.net header.i=@mxes.net header.b="DadxZHrP"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id 43E7D9C668; Thu, 14 May 2020 22:25:20 +1000 (AEST) Received: from smtp-out-4.mxes.net (smtp-out-4.mxes.net [198.205.123.69]) by minnie.tuhs.org (Postfix) with ESMTPS id 3DBD49C668 for ; Thu, 14 May 2020 22:25:19 +1000 (AEST) Received: from squirrelmail.mxes.net (squirrelmail.mxes.net [198.205.123.113]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPS id 5D6D77595B; Thu, 14 May 2020 08:25:17 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mxes.net; s=mta; t=1589459117; bh=Mtfl3pfA4+5mlVl1vnM/s1jEHAc+xoYEq/5UkKhPJQs=; h=Message-ID:In-Reply-To:References:Date:Subject:From:To: MIME-Version:Content-Type; b=DadxZHrPcdC22Z00MZ3jfLzjoP4RkkN52lZgyKQbOOYZI3s7gxmvWHKrGR3beg3/w Q0hb7m46uY4ipsCFhhdzTo4lAwLdvnu3ERyPJsJT1E7PRnN50AlA2Po8rfIkstjY9J zLuv3s0QgetkUEBs6B8N2M1GT6O91YGOhI0Ht/fA= Received: from squirrelmail.tuffmail.net (squirrelmail.mxes.net [198.205.123.113]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by squirrelmail.mxes.net (Postfix) with ESMTPSA id 9243775AE8; Thu, 14 May 2020 08:25:16 -0400 (EDT) Message-ID: <3f3cebe6682520577ccab2f1b81627cc.squirrel@squirrelmail.tuffmail.net> In-Reply-To: References: <3cb1126796176debe28aa66672ba27ae@yaccman.com> <20200511005745.GL17035@mcvoy.com> <357EFE54-BD94-4C10-8C43-C6735BF7D317@via.net> <20200511202555.GU17035@mcvoy.com> <71163EB4-683D-47DE-AAE2-93BF55C483E6@cfcl.com> Date: Thu, 14 May 2020 08:25:16 -0400 From: ron@ronnatalie.com To: "Dave Horsfall" User-Agent: SquirrelMail/1.4.23 MIME-Version: 1.0 Content-Type: text/plain;charset=utf-8 X-Priority: 3 (Normal) Importance: Normal Content-Transfer-Encoding: quoted-printable X-Sent-To: Subject: Re: [TUHS] v7 K&R C X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: The Eunuchs Hysterical Society Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" > On Wed, 13 May 2020, Rich Morin wrote: > >> A Fortran implementation I used years ago kept constants in a "literal >> pool". So, if you called a subroutine, passing in a constant, there w= as >> a possibility that the constant might be modified upon the routine's >> return. I don't recall this ever causing a problem in practice, but t= he >> possibility was amusing... > > As I dimly recall, Fortran has always used call by value/result (or > whatever the term is). So, if you modify an argument that happened to = be > passed as a constant... > Fortran argument passing to functions is call by reference. Some compilers had a non-standard exception to allow call by value.