Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!midway!quads.uchicago.edu!jcav
From: jcav@quads.uchicago.edu (john  cavallino)
Newsgroups: comp.sys.mac.apps
Subject: Re: Excel on LC...the FPU question
Keywords: Excel,FPU
Message-ID: <1991Apr25.213253.21845@midway.uchicago.edu>
Date: 25 Apr 91 21:32:53 GMT
References: <4497@ac.dal.ca> <42004@netnews.upenn.edu>
Sender: news@midway.uchicago.edu (NewsMistress)
Organization: University of Chicago
Lines: 18

In article <42004@netnews.upenn.edu> alex@eniac.seas.upenn.edu (Edmund Davis) writes:
>In fact, the same problem occurs on the LC.  Until the new macs came
>out, Microsoft (among other) assumed that any machine with a 68020 or
>better would certainly have an FPU.  Apple cut the FPU from the LC
>and IIsi in order to bring the price down.

{$SETC __flame__=TRUE}

And Microsoft and the others were inexcusably wrong to do so.  Since there
have been Macintosh FPUs there have been supported ways to use the OS to
check for their presence.  Apple has ALWAYS said "check for specific
functionality".  I believe it is also true that Apple at one time said all
machines with >= 68020 would have FPUs, but since the specific FPU check is
just as easy as the specific processor-type check, there really is no excuse.

{$SETC __flame__=FALSE}

(yes, I'm a Pascal weenie.  So sue me :-)