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,ca9eef4d5e2078ea
X-Google-Attributes: gid103376,public
From: Brian Rogoff <bpr@shell5.ba.best.com>
Subject: Re: Beware: Rep spec on an enumeration type causes code explosion
Date: 1997/12/16
Message-ID: <Pine.BSF.3.96.971216140840.24368A-100000@shell5.ba.best.com>#1/1
X-Deja-AN: 298828581
References: <dewar.881948014@merv> <EL972L.6B2.0.-s@inmet.camb.inmet.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Trace: 882311137 20659 bpr  206.184.139.132
Newsgroups: comp.lang.ada
Date: 1997-12-16T00:00:00+00:00
List-Id: <comp.lang.ada>


On Mon, 15 Dec 1997, Tucker Taft wrote:
> <snip>
> 
> Other examples where this principle was violated are with generics,
> where some compilers macro-expand and others (partially or universally)
> share, exceptions, where some compilers introduce an overhead on

I haven't seen any descriptions of the compiler techniqes used to do 
partial sharing of generic instantiations. Any references available?

-- Brian