MSF 5.1 does create real Windows programs. They run under Windows, taking
advantage of Windows's memory management and multitasking. They do not
run under DOS. They do not, however, provide hooks into the Windows API.
All you get for a user interface is a text window providing TTY I/O. If
you want a GUI, you need to do that in C or Visual Basic or some other
compiler that really does access the GUI.
This is a 16 bit compiler, so 32 bits is not on the table.
My opinion is that MSF 5.1 is appropriate for Windows if you've done the
user interaction with a GUI-supportive package, but have a calculation
module that wants to be done in Fortran. A couple of my colleagues did
just that with a program to compute noise in military airspaces. There is
a nice GUI C program that makes entering the data (forms inputs, drawing
boundaries and targets, etc.) reasonably fun. The noise calculation
module is done in Fortran, and for the Windows environment is built as a
quick-win app. The calculation module exploits existing working (and
policy compliant!) Fortran code, and is pretty well firewalled from GUI
fashions.
Ken Plotkin
1. These programs I write, let's say with 5.1, are they
'really' Win-programs or just 'dos-programs' (via
PIF). I mean is there somekind of extension for
windows enviroment?
2. Hardware? How much memory etc?
3. 32-bit application?
Thanks in advance,
- Petri -
>In article <HAKOLA.95...@lk-hp-19.hut.fi>,
>Petri Hakola <Petri....@hut.fi> wrote:
>>
>> I have few questions about f77-compliers in Windows 3.x
>[snip]
>MSF 5.1 does create real Windows programs. They run under Windows, taking
>advantage of Windows's memory management and multitasking. They do not
>run under DOS. They do not, however, provide hooks into the Windows API.
>All you get for a user interface is a text window providing TTY I/O. If
>you want a GUI, you need to do that in C or Visual Basic or some other
>compiler that really does access the GUI.
>.....
>Ken Plotkin
If I remember correctly, MSF 5.1 can use the Windows API, it's just
someone has to write the appropriate definition (.FD) and interface
(.FI) files to put into the program. I saw someone did that for
Windows 3.0. Of course, it is a lot easier to use Visual Basic or C to
do the GUI part these days.
Tzong-Tsong Miau