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=1.1 required=5.0 tests=BAYES_40,INVALID_DATE
	autolearn=no autolearn_force=no version=3.4.4
Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!ihnp4!chinet!nucsrl!gore
From: gore@nucsrl.UUCP
Newsgroups: comp.lang.ada
Subject: Re: single valued variables
Message-ID: <3930006@nucsrl.UUCP>
Date: Wed, 8-Apr-87 14:29:30 EST
Article-I.D.: nucsrl.3930006
Posted: Wed Apr  8 14:29:30 1987
Date-Received: Sat, 11-Apr-87 15:33:08 EST
References: <8704031535.AA26545@ucbvax.Berkeley.EDU>
Organization: Northwestern U, Evanston IL, USA
List-Id: <comp.lang.ada>

/ nucsrl:comp.lang.ada / "SVDSD::PETCHER@ti-eg.CSNET" /  6:14 am  Apr  3, 1987 /
>[...]  A variable that can have only one value is, by definition, not 
>a variable, but a constant.  In that context, it seems a compiler should 
>create a constant, issue a diagnostic for any subsequent code that attempts to 
>change the constant, and generate no executeable code for same.  [...]

A variable that can have at most one value can also have no value -- it may be
uninitialized; constants may not be.

Jacob Gore
Northwestern University, Computer Science Research Lab
{ihnp4,chinet}!nucsrl!gore