Newsgroups: comp.lang.smalltalk
Path: cantaloupe.srv.cs.cmu.edu!rochester!udel-eecis!news.mathworks.com!newsfeed.internetmci.com!swrinde!elroy.jpl.nasa.gov!sdd.hp.com!col.hp.com!news.dtc.hp.com!hplntx!hplb!tgg
From: tgg@hplb.hpl.hp.com ()
Subject: Re: Dolphin Smalltalk
Sender: news@hplb.hpl.hp.com (Usenet News Administrator)
Message-ID: <DuDECE.Eso@hplb.hpl.hp.com>
Date: Thu, 11 Jul 1996 08:31:26 GMT
References: <31CC4ABE.6DDE@individual.com> <31D1BF28.3BFF@terracom.net> <4qvhgm$c8m@news-old.tiac.net> <VBJ34DAYz60xEweW@blmsbury.demon.co.uk> <4ra4kl$21u@news-old.tiac.net> <836827340.3993.2@intuitiv.demon.co.uk> <31E1EF27.4B1B@concentric.net> <31E22411.4145@concentric.net> <31E259F3.6557@concentric.net>
Nntp-Posting-Host: thegnome.hpl.hp.com
Organization: Hewlett-Packard Laboratories, Bristol, England
X-Newsreader: TIN [version 1.2 PL0.7]
Lines: 25

This comment is more or less implicitly contained  in other  comments,
but I'll add it anyway...

Given that 
	- some  people  want  a delivery engine with a  small  memory
	  footprint, and  
	- others want to have speed of execution  at  all costs,
would it be possible for the user/designer to
	- specify the size of the method cache, or
	- specify a speed/size tradeoff,
	- either on the fly, or when the application is invoked

Good luck with the product. I hope that in the long term you manage to
keep the balance between:
	- a small, cheap, low footprint "personal" product
	- a fully-functioned, large footprint "corporate" product

--
===============================================================================
            The above are my own views, not the views of HP
  Tom Gardner                 Hewlett Packard Laboratories, Filton Rd, 
  tgg@hplb.hpl.hp.com	      Stoke Gifford, Bristol, Avon, BS12 6QZ, ENGLAND.
  Fax: +44 117 9228920        Tel: +44 117 9799910 ext. 28192
===============================================================================

