Newsgroups: comp.lang.smalltalk
Path: cantaloupe.srv.cs.cmu.edu!bb3.andrew.cmu.edu!newsfeed.pitt.edu!scramble.lm.com!news.math.psu.edu!chi-news.cic.net!nntp.coast.net!howland.reston.ans.net!ix.netcom.com!netcom.com!sehyo
From: sehyo@netcom.com (Sehyo Chang)
Subject: Re: [VW] To become: or not to become: that is the question.
Message-ID: <sehyoDMzJJG.4q9@netcom.com>
Organization: NETCOM On-line Communication Services (408 261-4700 guest)
X-Newsreader: TIN [version 1.2 PL1]
References: <3124E9C8.6AA0@bridge.bellsouth.com>
Date: Sun, 18 Feb 1996 19:02:04 GMT
Lines: 28
Sender: sehyo@netcom20.netcom.com

Faisal Waris (faisal.waris@bridge.bellsouth.com) wrote:
: I am at a point in my application's design where the use of
: #become: seems a feasible solution.

: I can redesign the application to avoid using #become:.

: I have 2 questions:

: 1. Is acceptable to do a large number of #become:'s. What
: effect if any is there on the system (assuming the system is not
: restarted frequently)?

: 2. Should one avoid the use of #become: in general?

: Any help will be appreciated. Please email as well.

: Regards ... Faisal

You should avoid use of #become: much as possible. It's main
drawback is that it's slow(dependents on vendor's implementation)
and also it's kind of kludge if you know what I mean.  It's maybe
non-portable to other smalltalk. So unless 
you are doing system level hacking or exotic appplication, you shouldn't
be doing it.  

-- sehyo chang


