Path: utzoo!utgpu!watmath!clyde!att!pacbell!ditka!dasys1!ejablow
From: ejablow@dasys1.UUCP (Eric Robert Jablow)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Turbo C 2.0 and EMS
Message-ID: <8204@dasys1.UUCP>
Date: 9 Jan 89 07:10:57 GMT
References: <1624@bingvaxu.cc.binghamton.edu> <4330113@hpindda.HP.COM> <29154@tut.cis.ohio-state.edu>
Reply-To: ejablow@dasys1.UUCP (Eric Robert Jablow)
Organization: Big Electric Cat//SUNY at Stony Brook Math Dept.
Lines: 34

Some people have complained that their programming projects are too
big for TC2.0's integrated environment.  I'd like to put my own two
cents in.

Suppose you have a large project with lots of modules,
subroutines, etc.  Do you always edit them all at once, or do you
write the subroutines one at a time?  If the latter, then you don't
have giant projects all in memory at the same time, and you can use
the integrated environment anyway, using the following paradigm.
Say you are writing a function foo, taking two int variables and
returning a long.  Test it, not by running the main program and
using all the complexity of your entire project, but by writing a
"shell" around the routine foo as that will read in test data, run foo
on said data, print out the results, and loop.  That way, you get foo
to work right, and can use the integrated editor/debugger in its
development.  Then you use all thepower of the command-line version to
put them all together.

The major difference, I think, between the TC integrated environment
and the QC or WATCOM C integrated environments, (and I've never
used them, so don't take my word for it) is that the others restrict
you to just one memory model, while TC doesn't; you can choose
whatever is appropriate.  Thus, you can do much more of your
compilation through the screen-version, relying on the command version
for linking and putting things together.  You can also experiment with
the environment of your program much more; how big would foo be if
compiled for medium model, or small, or compact,...


-- 
Eric Jablow                      {allegra,philabs,cmcl2}!phri\
Big Electric Cat Public Unix           {bellcore,cmcl2}!cucard!dasys1!ejablow
New York, NY, USA	 	 
New address:	jessica!eric@sbee.sbcc.edu.