Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!bbn!bbn.com!levin
From: levin@bbn.com (Joel B Levin)
Newsgroups: comp.sys.mac
Subject: Re: MPW C 3.0 Help!
Message-ID: <38303@bbn.COM>
Date: 5 Apr 89 19:05:07 GMT
References: <38240@bbn.COM> <1353@ndmath.UUCP>
Sender: news@bbn.COM
Reply-To: levin@BBN.COM (Joel B Levin)
Distribution: usa
Organization: BBN Communications Corporation
Lines: 29

In article <1353@ndmath.UUCP> dierks@ndmath.UUCP (Tim Dierks) writes:
|From article <38240@bbn.COM>, by levin@bbn.com (Joel B Levin):
|>In article <38226@bbn.COM> levin@BBN.COM (Joel B Levin) writes:
|>>In article <1748@amelia.nas.nasa.gov> prabhu@amelia.nas.nasa.gov (Dinesh K. Prabhu) writes:
|>>>     I recently got MPW C(3.0) and I am planning on switching to that
|>>>   environment. Could someone give me helpful tips on converting LSC 3.0
|>>
|>> [ Notes about going from LSC to MPW]
|>
|> [More notes about LSC -> MPW]
|
|  One other thing is that Str255s are different: in LSC, they're
|arrays of characters, in MPW, they're a struct, which means you
|occasionally have to do different things to them.  The most annoying,

Aha! that's what was great about MPW 3 C!  Strings are defined as
unsigned char[N], so LSC code works directly.  The other thing that
made porting LSC code relatively easy was that they also went back to
the canonical forms of Toolbox and OS calls; the C versions with glue
now are all lowercase.  I did some porting of LSC to MPW 2.0.2 C and
this was a royal pain (actually only the strings were, because a
version of Earle Horton's compatibility #include file allowed the use
of the canonical forms).

	/JBL


UUCP:     {backbone}!bbn!levin		POTS: (617) 873-3463
INTERNET: levin@bbn.com