Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!emory!mephisto!mcnc!ncsuvx!news
From: bank@lea.ncsu.edu (Dave The DM)
Newsgroups: comp.os.msdos.programmer
Subject: Re: MSC 6.0 / PWB quirks
Message-ID: <1990Sep29.060422.7362@ncsuvx.ncsu.edu>
Date: 29 Sep 90 06:04:22 GMT
References: <834@intelhf.hf.intel.com>
Organization: Leazar Hall MicroVax II (CSCLEA), NCSU, Raleigh NC
Lines: 21


    I have MS C 6.0 (in fact, I'll shortly be Posting a question about
MS C myself) but I don't use PWB. The problems you cite are one reason.
 
    However, I have a pretty good idea as to how to workaround your
problem with setting flags on MASM when compiling inside PWB. What
Microsoft usually does is look for environment variables. As an 
example, you can set the command-line parameters for CL (the 
compiler) just by typing "CL=/AL /FPi" at your DOS prompt. In this case,
I've instructed the compiler to use the large memory model and to use
the floating-point library that supports both the 80x87 and emulation.
Now I don't have to specify those things when I compile (altho if I DO
specify command-line parameters when I compile, they override and
conflicting ones present in the environment variable).
 
   What the name of the environment variable is for MASM I haven't
the faintest idea. Try checking the docs. But I do know that this
feature is pretty consistent thru the MS line of compilers -- I 
have a FORTRAN compiler of theirs that does things the same way.
 
                                          Dave the DM