Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!ames!apple!usc!bbn!bbn.com!levin
From: levin@bbn.com (Joel B Levin)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Think's LSC generates slow code in comp with MPW C
Message-ID: <43090@bbn.COM>
Date: 21 Jul 89 17:43:13 GMT
References: <1630@eds.ericsson.se> <1853@cbnewsc.ATT.COM> <12252@eddie.MIT.EDU> <1331@draken.nada.kth.se>
Sender: news@bbn.COM
Reply-To: levin@BBN.COM (Joel B Levin)
Organization: BBN Communications Corporation
Lines: 29

In article <1331@draken.nada.kth.se> d88-jwa@nada.kth.se (Jon W{tte) writes:
|Just how much trouble is it really, compiling a finished program in
|MPW when it's written in LSC. Couldn't be all that hard, could it ?
|But then, you'd have to maintain two compilers :-(
|
|Curious minds (including mine) want to know...

*With a little planning*, very easy I should think (especially with
MPW 3).  If you know you are going to do this, you can build in the
compatibility.  Something like

  #ifdef MPW
  typedef short Integer;
  #else
  typedef int   Integer;
  #endif

and always use Integer instead of int in LSC.  Also, most of the MPW
<Foo.h> files are (a different set of) <FooMgr.h> files in LSC.  So
you may have to maintain two lists under conditionals.  Or two
separate ".h" files.

Disclaimer: my experience is from porting some LSC code to MPW, not
from actually trying to write compatible/portable code, since I don't
have LSC.
=
UUCP:     levin@bbn.com (new) or {backbone}!bbn!levin (old)
INTERNET: levin@bbn.com       		POTS: (617) 873-3463
   "The night was"