Path: utzoo!attcan!uunet!tank!ncar!unmvax!tut.cis.ohio-state.edu!baseball.cis.ohio-state.edu!macgyver
From: macgyver@baseball.cis.ohio-state.edu (wilson s liaw)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Lightspeed C, MPW and TIFF
Keywords: source code, porting
Message-ID: <51550@tut.cis.ohio-state.edu>
Date: 9 Jun 89 08:23:29 GMT
References: <12075@well.UUCP>
Sender: news@tut.cis.ohio-state.edu
Reply-To: wilson s liaw <macgyver@cis.ohio-state.edu>
Distribution: comp
Organization: Ohio State University Computer and Information Science
Lines: 34

In article <12075@well.UUCP> chris@well.UUCP (Chris Sears) writes:
>...........
>    1.  Is there a straightforward path for porting from MPW to Lightspeed?
>        Why is it that they are so different?  In 100 words or less, is
>        there a good reason for me to use MPW?
>
>    2.  Does anyone have a Lightspeed TIFF library?  Is the Aldus TIFF
>        library Lightspeed or MPW?


	Being a ownner of both LSC and MPW C, I thought I post a couple of
the major difference. (I am afraid that there is no strightforward path
for porting.)

	1: the size of int is different, in LSC, a int is 16 bits, MPW C, int
	   is 32 bits.
        2: InitGraf(&thePort) in LSC is InitGraf(&qd.thePort) in MPW C.
	3: the way they handle segment is very different, since you have
 	   LSC, I won't explain how LSC handles it, in MPW whenever you 
	   want to create a new segment, you put 
	   #pragma segment Main
           in your source code file. Thus, you can have lots of segments
	   in a file.

 	   I can't think of anything else at this time. Good luck on the 
convernsion.

				Wilson

-=-
Wilson M. Liaw                            $  Two sure ways to tell a sexy male;
Internet : macgyver@cis.ohio-state.edu    $  the first is, he has a bad memory.
UUCP     : osu-cis!tut!macgyver           $  I forget the second :)
CompuServe : 71310,1653  GEnie : W.Liaw   $