Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!phcalamai
From: phcalamai@water.UUCP
Newsgroups: comp.sys.ibm.pc
Subject: Question about CodeView
Message-ID: <894@water.UUCP>
Date: Mon, 6-Apr-87 11:54:51 EST
Article-I.D.: water.894
Posted: Mon Apr  6 11:54:51 1987
Date-Received: Mon, 6-Apr-87 23:45:45 EST
Reply-To: phcalamai@water.UUCP (Paul H. Calamai)
Distribution: world
Organization: U. of Waterloo, Ontario
Lines: 18
Summary: Is there really different versions for MS Fortran and MS C ?


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?

THANKS....Paul Calamai.