Path: utzoo!attcan!uunet!mcvax!enea!tut!santra!jmunkki
From: jmunkki@santra.HUT.FI (Juri Munkki)
Newsgroups: comp.sys.mac.programmer
Subject: Re: LSC 3.0
Message-ID: <15051@santra.UUCP>
Date: 2 Aug 88 14:53:41 GMT
References: <327@ncar.ucar.edu> <730034@hpcilzb.HP.COM> <7763@cup.portal.com>
Sender: jmunkki@santra.UUCP
Reply-To: jmunkki@santra.UUCP (Juri Munkki)
Organization: Helsinki University of Technology, Finland
Lines: 32

In article <7763@cup.portal.com> Thomas_E_Zerucha@cup.portal.com writes:
>Wouldn't it have been better to have a two level upgrade, say $30 for the
>LSC 3.0 upgrade and $40 for the debugger?  It seems that very few users
>have (or will have until the chip prices drop) 2 Meg, that to charge $70
>for an upgrade, half of which is useless to the majority of people is what
>is being complained about.  If you had split it, then you could pay a little
>now for what you could use, and the rest later when you have upgraded your
>computer to be able to use it.

		YOU CAN USE THE DEBUGGER IN 1M!
	You will want to use it even if you have only 1M.
			     AND
	    Yes, it is as good as they say it is...

I have a Mac 2 with 2MB and until yesterday I had never considered
using MultiFinder while developing. The ComputerWare shipment that
arrived yesterday contained LSC3.0 and the debugger made me change
my mind. It is wonderful.

I still want to have 020 and 881 opcodes for the assembler and I'd
like to be able to type register names into a data window. You can't
currently see the contents of D0 or A0, unless you drop into TMON.
In addition to being a good C source code debugger, the debugger is
a superb assembly debugger (symbolic beyond your wildest dreams).

I also wish a future version will not use subroutine calls for the
C math calls. It shouldn't be hard to extend the compiler so that
all common calls generate FPU code.

Juri Munkki
jmunkki@santra.hut.fi
jmunkki@fingate.bitnet