Newsgroups: comp.lang.smalltalk
Path: cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!oitnews.harvard.edu!purdue!ames!enews.sgi.com!news.sgi.com!news.maxwell.syr.edu!metro.atlanta.com!news.new-york.net!nonexistent.com!not-for-mail
From: Timothy Reaves <reaves@unix.asb.com>
Subject: Re: [VA] Should classes be SmallTalk or non-visual parts?
Content-Type: text/plain; charset=us-ascii
X-Nntp-Posting-User: (Unauthenticated)
Reply-To: reaves@unix.asb.com
Content-Transfer-Encoding: 7bit
Message-ID: <E6LGIq.FC6@nonexistent.com>
References: <E6JMnt.KLr@nonexistent.com> <331CE9BE.3382@silvermark.com>
X-Mailer: Mozilla 2.02E (OS/2; I)
Mime-Version: 1.0
X-Trace: 857605345/19374
X-Nntp-Posting-Host: sls51.asb.com
Date: Wed, 5 Mar 1997 23:42:20 GMT
Lines: 11

Michael Silverstein wrote:
--snip--

> As a side note - if your coding is outside of the Abt hierarchy, the
> VisualAge editors are still useful for autogenerating get/set selectors
> and instance variables. Just make sure you don't let the editor
> automatically define the attribute-changed event signal, or you'll
> needlessly defeat a compiler optimization.
> 

     I don't follow what you're saying here. Could you please eleborate?
