From xemacs-m  Sun Mar 23 13:10:31 1997
Received: from crystal.WonderWorks.COM (crystal.WonderWorks.com [192.203.206.1])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id NAA07844
	for <xemacs-beta@xemacs.org>; Sun, 23 Mar 1997 13:10:29 -0600 (CST)
Received: by crystal.WonderWorks.COM 
	id QQcido20311; Sun, 23 Mar 1997 14:10:28 -0500 (EST)
Date: Sun, 23 Mar 1997 14:10:28 -0500 (EST)
Message-Id: <QQcido20311.199703231910@crystal.WonderWorks.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: Kyle Jones <kyle_jones@wonderworks.com>
To: XEmacs Developers <xemacs-beta@xemacs.org>
Subject: Re: Buffer-specific display-tables 
In-Reply-To: <199703231904.NAA07762@xemacs.org>
References: <QQciav01127.199703230118@crystal.WonderWorks.COM>
	<199703231904.NAA07762@xemacs.org>
X-Mailer: VM 6.22 under 19.15 XEmacs Lucid (beta103)
X-Face: /cA45WHG7jWq>(O3&Z57Y<"WsX5ddc,4c#w0F*zrV#=M
        0@~@,s;b,aMtR5Sqs"+nU.z^CSFQ9t`z2>W,S,]:[+2^
        Nbf6v4g>!&,7R4Ot4Wg{&tm=WX7P["9%a)_da48-^tGy
        ,qz]Z,Zz\{E.,]'EO+F)@$KtF&V

Chuck Thompson writes:
 >     Kyle> at the top.  It is not immediately obvious whether this is a
 >     Kyle> bad thing to do at the particular point in the redisplay
 >     Kyle> code where get_display_table() is called.  But it probably
 >     Kyle> is.
 > 
 > There is no probably about it.  The call to get_display_table is in
 > what is pretty much the heart of the redisplay engine.  The Second
 > Rule of Redisplay is definitely in effect.  Perhaps more accurately
 > the First Corollary of the Second Rule which is 'Thou Shalt Not GC

Something has got to give.  The display code need to reference
specifiers.  specifier_instance can call eval, which means it can
GC.  So I think the instantiators that can call eval have got to
go.

