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.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM
	autolearn=unavailable autolearn_force=no version=3.4.4
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!aioe.org!.POSTED!not-for-mail
From: Victor Porton <porton@narod.ru>
Newsgroups: comp.lang.ada
Subject: Why stack can hold indefinite objects but records cannot?
Date: Tue, 28 Nov 2017 22:31:01 +0200
Organization: Aioe.org NNTP Server
Message-ID: <ovkh24$1bh5$1@gioia.aioe.org>
NNTP-Posting-Host: edFHTOfx8phAphItWrZ8cQ.user.gioia.aioe.org
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7Bit
X-Complaints-To: abuse@aioe.org
User-Agent: KNode/4.14.10
X-Notice: Filtered by postfilter v. 0.8.2
Xref: reader02.eternal-september.org comp.lang.ada:49221
Date: 2017-11-28T22:31:01+02:00
List-Id: <comp.lang.ada>

Why is it OK to create an indefinite object as a local variable ("on stack") 
but not OK to put an indefinite object into a record?

How records are less powerful than the stack?

By the way, how indefinite local variables can be implemented? (just 
curious)

Moreover, wouldn't it to be a good idea to allow indefinite objects in 
records (thus making the record itself indefinite, even if it has no 
discriminants)? I realize that then it would be difficult to track which 
records are definite and which indefinite. But what's about the idea?

-- 
Victor Porton - http://portonvictor.org