Path: utzoo!utgpu!watmath!clyde!att!rutgers!ukma!tut.cis.ohio-state.edu!dinghy.cis.ohio-state.edu!schanck From: schanck@dinghy.cis.ohio-state.edu (Christopher Schanck) Newsgroups: comp.sys.ibm.pc Subject: Re: Turbo C 2.0 and EMS Message-ID: <29045@tut.cis.ohio-state.edu> Date: 4 Dec 88 06:47:17 GMT References: <1624@bingvaxu.cc.binghamton.edu> Sender: news@tut.cis.ohio-state.edu Organization: The Ohio State University Dept of Computer and Information Science Lines: 32 In article <1624@bingvaxu.cc.binghamton.edu> vu0112@bingvaxu.cc.binghamton.edu (Cliff Joslyn) writes: > >So I have TC 2.0 and I just got 256K of EMS, and I *really* want to be >able to use it during compilation and linkage in the integrated From what I understand, only the editor workspace can be put into EMS; other than that, you are out of luck. >some 300K for the user's program, with debug code. This seems to leave >the integrated debugger useless for seriously large code unless TC 2.0 >can use above 640K. You got it; that is the reason for the higher-priced "Professional" package with the command line debugger. The integrated environment is a real pain for large stuff. Personally, I want *my* favorite editor, so I use command line, which means I would need to buy the Professional package, which I can't afford since I am a poor grad student. Gee, remember when Borland was the company that gave you far more then you could want for $49.95? Somebody ought to tell Phillippe that integrated environments are not the be-all, end-all of programming. Turbo Pascal was a hit more because it was a quality Pascal compiler for $50 than because of the environment. In fairness, I have to point out that without a hard drive, the integrated environment is the only way to go. Chris -=- "My brain is NOT a deadlock-free environment!!!!" --- Christopher Schanck, mammal at large. schanck@flounder.cis.ohio-state.edu