tim@watson.bcm.tmc.edu (Timothy Owen Lesniak) (09/09/90)
I'm new to Microsoft C. What I'd like to do is be able to compile programs in the background while working on other stuff. So far, I've been using the Program Work Bench to edit, compile, and link my programs. What I'd like to know is what is the best way to run this under Windows. I have gotten "Application Violates ...Memory" errors on occation. Can someone who has had more success tell me: 1. Would background compilations work better (take less memory, run faster) if I did not compile from the Workbench. 2. If using the Workbench is acceptable, what should I set the PIF settings to (i.e. how much memory is _required_ for the Workbench to run the compilations so I can figure out how much I have to run other applications). Thanks! Tim Lesniak Baylor College of Medicine tim@bcm.tmc.edu
spolsky-joel@cs.yale.edu (Joel Spolsky) (09/09/90)
In article <1890@gazette.bcm.tmc.edu> tim@watson.bcm.tmc.edu (Timothy Owen Lesniak) writes: | 1. Would background compilations work better (take less memory, run faster) | if I did not compile from the Workbench. Yes, in fact, I think that the PWB is the slowest possible way to develop! Anyway, it is redundant under windows; I recommend just running your favorite editor (even PWB) in one window, then write a nice makefile, and add "Make" to the program manager, with an appropriate PIF... Much faster than making the stupid PWB, which always thinks it must swap itself in and out, start the make for you. PS, the Windows Software Development Kit includes a document on-line which describes using PWB under windows. It is called PWBINFO.WRI; it is explicitly copyright so I can't post it here. It doesn't mention anything about PIF's; I guess the defaults would be OK. Joel Spolsky spolsky@cs.yale.edu Talk Hard.