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.8 required=5.0 tests=BAYES_00,INVALID_DATE,
	MSGID_SHORT autolearn=no autolearn_force=no version=3.4.4
Path: utzoo!attcan!uunet!husc6!bloom-beacon!tut.cis.ohio-state.edu!mailrus!cornell!uw-beaver!fluke!ssc-vax!adolph
From: adolph@ssc-vax.UUCP (Mark C. Adolph)
Newsgroups: comp.lang.ada
Subject: Read-Only Variables
Message-ID: <2125@ssc-vax.UUCP>
Date: 27 Jul 88 17:40:42 GMT
Organization: Boeing Aerospace Corp., Seattle WA
List-Id: <comp.lang.ada>

We've come across an interesting problem here.  We're trying to build a
model of a processor that we can use in simulation.  In at least one
case, we have a register with bits that, in the hardware, can be read by
software but only modified by hardware.  How does one declare a record
component that is only visible for reading but can be updated
internally?  Making it private and declaring a function to allow reading
isn't appropriate as it would not be a correct model of the situation.

-- 

					-- Mark A.
					...uw-beaver!ssc-vax!adolph