Path: utzoo!attcan!uunet!cbmvax!ulowell!hawes
From: hawes@dino.ulowell.edu (Bill Hawes)
Newsgroups: comp.sys.amiga
Subject: Re: DMouse artifact (was: Re: ConMan Question)
Message-ID: <1992@dino.ulowell.edu>
Date: 6 Jul 88 23:32:20 GMT
References: <8806300744.AA14596@cory.Berkeley.EDU>
Reply-To: hawes@dino.ulowell.edu (Bill Hawes)
Organization: University of Lowell Productivity Center, Lowell MA.
Lines: 15



I'm certainly in favor of minimizing the amount of memory used by software,
one of the main reasons I choose to code in assembly language.  On the other
hand, since DMouse potentially replaces several other background-type goodies,
Matt has already saved memory by combining the functionality.  But if people
are going to have to use PopCLI II to get the search path, wouldn't it be
better to use a CLI for DMouse?

The limit of 20 CLI's doesn't seem too severe -- the only time I've hit it
is when purposely testing something for that failure mode, or when debugging
a program that keeps hanging, so that it's easier to keep grabbing CLI's
(using PopCLI II) rather than rebooting.

  -Bill