Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!ames!ucbcad!ucbvax!cbatt!ihnp4!homxb!mrw
From: mrw@homxb.UUCP (M.WHITNEY)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Question about CodeView
Message-ID: <238@homxb.UUCP>
Date: Tue, 21-Apr-87 09:46:46 EST
Article-I.D.: homxb.238
Posted: Tue Apr 21 09:46:46 1987
Date-Received: Wed, 22-Apr-87 05:34:10 EST
References: <894@water.UUCP>
Distribution: world
Organization: AT&T Bell Laboratories, Holmdel
Lines: 25
Summary: Fortran CV works on C programs

In article <894@water.UUCP>, phcalamai@water.UUCP writes:
> 
> I recently upgraded to the latest verion of MicroSoft's Fortran and
> I'm preplexed by a statement in their README.DOC. It says, and I quote:
> 
> When using the Microsoft FORTRAN version of the Microsoft CodeView (TM)
> Debugger, you must set the PATH environment variable so that the FORTRAN
> version of the CV.EXE file is the first version found in the path.
> Setting PATH in this way ensures that you do not use a different version
> of CV.EXE (for example, the CV.EXE file for Microsoft C) with Microsoft
> FORTRAN programs.
> 
> If this is truly a problem why on earth did Microsoft not call these
> two incantations of CV something like CVC.EXE and CVFORT.EXE to avoid
> any conflict and eliminated the need for the setting of PATH?
> 
> Is this really a problem? Is there a simple work-around?

Yes - the CodeView(TM) that comes with Microsoft Fortran also works on
Microsoft C.  Therefore, just trash the version that came with the C
compiler.

             Ken Becker   hotlv!kab

The opinions expressed above are mine, and not those of my employer.