Frequently Asked Questions for Fortran PowerStation 32

• Microsoft FORTRAN PowerStation 32 for Windows NT and Windows 95, version 4.0

SUMMARY

The following is a list of Frequently Asked Questions (FAQs) about Microsoft Fortran PowerStation.

MORE INFORMATION

Q. Can I install Fortran PowerStation on a network?

A. Yes, you can. Instructions for installing and administering Fortran PowerStation on a network are located in the file \FPSSETUP\NETWORK.BAT. Network installation is only possible with the Fortran PowerStation CD.

Q. When I uninstall the product using the Remove All option, why does the FPSSetup directory remain in the Fortran PowerStation program group in Windows NT 3.51?

A. Uninstall does not remove the FPSSetup directory on Windows NT 3.51. This is the way the setup works. The SETUP.EXE file itself is deleted properly, but not the \FPSSETUP directory.

Q. Can I create a change or create a new project type based on an existing project?

A. If you have a project of one type, such as a console application, and you want to change it to another type, such as QuickWin, you must start over. The same applies if you have a project that you want to use as the basis for another similar project of a different type.

Q. How do the keywords get colored in Microsoft Developer Studio?

A. By design, the keywords are colored without any knowledge of context. Microsoft Developer Studio has no compiler parser. For example, if you have a variable with the name "end", it will be colored because there is a valid statement with the same name.

Q. Is syntax code coloring available for user-defined types?

A. No, the code coloring is not available for user-defined data types.

Q. Can I save the Watch or Variables windows in the debugger?

A. In the past you were able to save the various windows that the debugger used as files. You can no longer do this with the Watch and Variables windows. However, you can copy the content to the Clipboard and paste it in a file.

Q. How can I debug assumed-size arrays?

A. When you display an assumed-size array, it expands to display the first element of the left-most index. If, for example, you have an array A(3), you only see A(1) in the array expansion in the Watch, Quickwatch, and Variables windows. If, on the other hand, you have a multidimensional array such as A(2,2,2) when it is expanded, you see A(1,1,1), A(2,1,1), A(1,2,1), A(2,2,1). Assumed-size arrays have many restrictions on them in source code. If you want to look at the rest of the array, you need to use the Memory window.

Q. If you have a DO loop and set a breakpoint on the DO line, the breakpoint only stops the first time through when debugging. For example, if I said DO N=1,100, I would expect to stop on the line 100 times, yet I only stop there once. Why does this occur?

A. A debug source line consists of zero or more assembly lines. When you set a breakpoint on a source line, a breakpoint is set on the first instruction in a group of assembly instructions. A simple DO loop consists of about a dozen assembly lines. The first half sets up the variables and the last half decrements the variables and checks for loop termination. When you set a breakpoint on the source line, you are actually setting a breakpoint on the initialization code. If you step through this in disassembly mode you can follow what is happening. If you want to set a breakpoint that stops at each loop iteration, you can do one of the following:

• Set the breakpoint on the first source line inside the DO loop.


- or -


• Select Disassembly from the View menu after the debugger has been started, and set the breakpoint on the loop code.

      INCLUDE 'FLIB.FI'
      INCLUDE 'FLIB.FD'
      PRINT*, 'Test'
      END

      LOGICAL*4 FUNCTION InitialMenu
      INCLUDE 'FLIB.FD'
      print*, 'Test'
      InitialMenu = .TRUE.
      END 

      type mytype
         integer a
         real b
      end type
      type (mytype) dummyarray(2)
      integer size
      size= loc(dummyarray(2)) - loc(dummyarray(1))
      print*, size 

      INTEGER I*4   !This is okay
      END

      INTEGER FUNCTION X()*4   !This causes a compilation error
      END 

     i=1
     RETURN   !This line produces a compilation error
     END 

      block data foo
      common /g/ i
      data i /1/ 
      end 

Command line warning D2009: unrecognized flag /F ignored.
Command line warning D2009: unrecognized flag /L ignored.
Command line error D2003: missing source filename

Additional query words: 4.00

Keywords : kbsetup kbCompiler kbFL32 kbFortranPS kbLangFortran
Version : :4.0
Platform : NT WINDOWS
Issue type :