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.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,2cb6bf1d75f9146b
X-Google-Attributes: gid103376,public
From: dewar@cs.nyu.edu (Robert Dewar)
Subject: Re: Freezing points
Date: 1996/02/18
Message-ID: <dewar.824674111@schonberg>#1/1
X-Deja-AN: 140002543
references: <leschkes.824503590@ferret> <DMzIA8.92J.0.-s@inmet.camb.inmet.com>
organization: Courant Institute of Mathematical Sciences
newsgroups: comp.lang.ada
Date: 1996-02-18T00:00:00+00:00
List-Id: <comp.lang.ada>

To add to Tucker's comments on freezing, one thing you will find helpful
is to understand the model behind the rules. Think of code being generated
for various constructs. Now sometimes you need to know the size and
representation of something to generate code, e.g. to generate code to
initialize an object of a type. That's what the freezing is fore, before
you can generate such code for a type, it must be frozen.