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.7 required=5.0 tests=BAYES_00,GAPPY_SUBJECT,
	INVALID_DATE autolearn=no autolearn_force=no version=3.4.4
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!bu.edu!inmet!stt
From: stt@inmet.inmet.com
Newsgroups: comp.lang.ada
Subject: Re: Types defining h/w r/o or w/o regis
Message-ID: <20600105@inmet>
Date: 1 Jun 91 10:01:00 GMT
References: <3949@titan.tsd.arlut.utexas.edu>
Nf-ID: #R:titan.tsd.arlut.utexas.edu:3949:inmet:20600105:000:413
Nf-From: inmet.inmet.com!stt    Jun  1 06:01:00 1991
List-Id: <comp.lang.ada>


Re: Read-only types

Rather than associating the Read-only-ness with the
type, I would associate it with the object.
The simplest implementation is to declare the object
in a package body, with an appropriate address clause,
and then define a parameterless function to return
the value of the object.  This function could be inlined.

S. Tucker Taft    stt@inmet.inmet.com
Intermetrics, Inc.
Cambridge, MA  02138