Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!alhena.usc.edu!ajayshah
From: ajayshah@alhena.usc.edu (Ajay Shah)
Newsgroups: comp.lang.c
Subject: Mixed development between SunOS and Turbo C
Message-ID: <32240@usc>
Date: 24 Apr 91 19:27:55 GMT
Sender: news@usc
Organization: University of Southern California, Los Angeles, CA
Lines: 26
Nntp-Posting-Host: alhena.usc.edu
Originator: ajayshah@alhena.usc.edu


I'm a relatively novice C programmer doing some numerical analysis.  
I like developing code on both the PC (Turbo C) and the Sun (gcc).  
I only do ANSI C.  My code involves no OS manipulations -- just 
churning matrices and floating point numbers.

Does someone have ideas on how to make this convenient?  I
recently took some source from the Sun to TurboC and it worked
flawlessly.  If I keep developing on TurboC, can I expect to take
source back to the Sun?  The only major difference I've found so
far is that TurboC gives a lot more error messages, something I
value immensely.  For surefire portability, I never read the TurboC 
manual.  I use K&R and H&S and write code just like I would on Unix.  

Is this a sound strategy?  Are there brilliant header files around 
which mitigate differences?

Thanks,

	-ans.

-- 
_______________________________________________________________________________
Ajay Shah, (213)734-3930, ajayshah@usc.edu
                             The more things change, the more they stay insane.
_______________________________________________________________________________