Lahey/Fujitsu Fortran v7.1

Fortran para arquitecturas .NET

Fortran for .NET allows you to create applications for the Microsoft .NET Framework. Lahey and Fujitsu have combined advanced compiler technology with support for Forms designers and Web Services to enable Fortran organizations to develop .NET applications with Fortran as easily as with other Microsoft .NET languages. Fortran for .NET consists of a Fortran compiler and associated tools designed to help you create applications that run in the .NET Framework.

• Fortran for .NET compiler
• Fortran for .NET language
• Visual Studio .NET integration
• Windows Forms
• ASP.NET Web Forms
• ADO.NET
• Fortran for .NET compiler options
• Restrictions on Fortran for .NET Code
• Hardware and software requirements for Enterprise and Academic Editions
• What can you do with Fortran for .NET and why would you want to?

The Fortran for .NET language system is included in LF Fortran v7.1 Enterprise and Academic editions.

Fortran for .NET compiler

The CLR does much more than provide the ability to operate on different operating systems, it also provides the basis for interoperability between different .NET languages, interlanguage debugging, versioning, and application deployment, among other things.

Applications that are targeted for the CLR are called managed applications, or managed code. Managed applications are required to be type safe and to present standardized interfaces, so that interoperability and security requirements can be met. Because some older Fortran features (such as COMMON and EQUIVALENCE) can violate the CLRs rules for type safety and interfaces, certain restrictions had to be placed on .NET applications that do not allow 100% compatibility with Fortran standards. For details on restrictions, see Restrictions on Fortran for .NET Code.

Fortran for .NET language

Tables in this section identify language support in the following categories:

Data Types
Operators
Arrays
Program units
Arguments and Interfaces
Declaration of Program Units, Variables and Attributes
Executable Statements
Object Oriented and .NET extensions
Numeric Functions
Mathematical Functions
Character Functions
Bit Manipulation Functions
Inquiry Intrinsic Functions
Data and Time Functions
Array Functions
Other Functions

Supported Data Types

Intrinsic Data Types	Supported?
INTEGER(KIND=1)	Yes
(KIND=2)	Yes
(KIND=4)	Yes
(KIND=8)	Yes
UINTEGER(KIND=1)	Yes
(KIND=2)	Yes
(KIND=4)	Yes
(KIND=8)	Yes
REAL(KIND=4)	Yes
(KIND=8)	Yes
(KIND=16)	No28
COMPLEX(KIND=4)	Yes
(KIND=8)	Yes
(KIND=16)	No28
LOGICAL(KIND=1)	Yes
(KIND=2)	Yes (treated as KIND=1)
(KIND=4)	Yes (treated as KIND=1)
(KIND=8)	Yes (treated as KIND=1)
CHARACTER(KIND=1)	Yes
Derived type	Yes
Literal Constants	Supported?
INTEGER(KIND=1)	Yes
(KIND=2)	Yes
(KIND=4)	Yes
(KIND=8)	Yes
UINTEGER(KIND=1)	Yes
(KIND=2)	Yes
(KIND=4)	Yes
(KIND=8)	Yes
REAL(KIND=4)	Yes
(KIND=8)	Yes
(KIND=16)	No28
COMPLEX(KIND=4)	Yes
(KIND=8)	Yes
(KIND=16)	No28
LOGICAL(KIND=1)	Yes
(KIND=2)	Yes (treated as KIND=1)
(KIND=4)	Yes (treated as KIND=1)
(KIND=8)	Yes (treated as KIND=1)
CHARACTER(KIND=1)	Yes
Binary	Yes
Octal	Yes
Hexadecimal	Yes
Derived Types38, 39, 40, 41, 46, 47	Supported?
Array component	Yes
ALLOCATABLE component	Yes
POINTER component	Yes
Component has derived type	Yes
default initialize	Yes14
Structure Constructors	Yes42

Supported Operators

Array Support

Supported Program Units

Support for Arguments and Interfaces

Support for Declaration of Program Units, Variables, and Attributes

Support for Executable Statements

Support for Object Oriented Extensions, .NET Extensions

Support for Numeric Intrinsic Functions

Support for Mathematical Intrinsic Functions

Support for Character Intrinsic Functions

Support for Bit Manipulation Intrinsic Functions

Support for Inquiry Intrinsic Functions

Support for Date and Time Intrinsic Subroutines

Support for Array Intrinsic Procedures

Support for Other Intrinsic Procedures

Project Management
To efficiently manage the items that are required by your development effort, such as references, data connections, folders, and files, Visual Studio .NET provides two containers: solutions and projects. An interface for viewing and managing these containers and their associated items, Solution Explorer, is provided as part of the integrated development environment (IDE).

Project/Code Templates
Project/code templates syntactically correct compilable source code shells and associated project setting that help you create applications or services. Fortran for .NET provides the following Visual Studio project types:

• The Empty Project template provides a solution and project without any source files or references. You can add items to this project by using the "Project/Add New Item" menu selection.
• The Class Library template consists of a library project and a skeletal Fortran class library containing a single static method. When compiled, this project type creates a .NET DLL file, which may be supplied as a reference to other .NET applications.
• The Console Application consists of a console project, and a skeletal main program. When compiled, this project type creates a console application. If this application is invoked from a console, it executes within the console. If the application is invoked from an icon, the Run menu, or Windows Explorer, it creates a console to run in, and destroys the console when the program completes execution.
• The ASP Web Application template is a Web Forms Designer project, which begins in design mode with a blank Web form. Controls may be dragged from the toolbox onto the form, and Fortran source code will be generated to implement the control. The project consists of an HTML web page that uses Fortran for .NET to provide the code behind.
• The ASP Web Service template is also a Web Forms Designer project in which the Web Form provides a user interface on the local machine, with Fortran for .NET powering the application on the server side.
• The Windows Application template is a Windows Form designer project, which begins in design mode with a blank form. Controls may be dragged from the toolbox onto the form, and Fortran source code will be generated to implement the control. This project type compiles into an event driven Windows application.
• The Setup and Deployment template allows the programmer to create installation programs that can ease the task of distributing .NET applications. A setup project packages the files that make up an application, facilitates the creation of directory structures, and provides a means of installing and registering assemblies.
• The Database template provides a means of manipulating databases and designing and executing SQL scripts and queries without having to create an application.

Fortran-Smart Editing
The Fortran for .NET language system provides the Visual Studio editor with the smarts to recognize and color-code Fortran language syntax.

Mixed-Language Debugging
Fortran for .NET code can be debugged in the Visual Studio debugger. If your application includes procedures written with other .NET languages, the Visual Studio debugger can seamless step from Fortran for .NET code to the other language code and back again.

A form is a bit of screen real estate, usually rectangular, that you can use to present information to the user and to accept input from the user. Forms can be standard windows, multiple document interface (MDI) windows, dialog boxes, or display surfaces for graphical routines. The easiest way to define the user interface for a form is to place controls on its surface.

Within a Windows Forms project, the form is the primary vehicle for user interaction. By combining different sets of controls and writing code, you can elicit information from the user and respond to it, work with existing stores of data, and query and write back to the file system on the user's local computer.

Although the form can be created entirely within the editor, it is easier to use the Windows Forms Designer to create and modify forms. Fortran for .NET's support for the Windows Forms Designer makes it easy for you to create Windows applications with Fortran.

ADO.NET cleanly factors data access from data manipulation into discrete components that can be used separately or in tandem. ADO.NET includes .NET Framework data providers for connecting to a database, executing commands, and retrieving results. Those results are either processed directly, or placed in an ADO.NET DataSet object in order to be exposed to the user in an ad-hoc manner, combined with data from multiple sources, or remoted between tiers. The ADO.NET DataSet object can also be used independently of a .NET Framework data provider to manage data local to the application or sourced from XML.

-addres ? specify .NET resource file name to embed
-[n]co ? display compiler options
-[n]cs ? case sensitive names
-[n]dbl ? extend single precision reals to double precision
-exe ? create .NET console executable
-[n]f95 ? F95 standard conformance warnings
-[n]fix ? fixed source form
-[n]g ? generate debugging information
-i ? specify directory containing include file
-[n]in ? default IMPLICIT NONE
-[n]info ? display informational messages
-library ? create .NET code library
-linkmod ? specify .NET module file name to link
-linkres ? specify .NET resource file name to link
-[n]long ? extend 4-byte integers to 8-byte
-main ? specify main entry point class method name
-[n]maxfatals ? specify maximum fatal error count before aborting
-ml ? specify Win32 mixed language target
-module ? create .NET module
-o0 ? no optimizations
-out ? specify output file name
-[n]passbyval ? default argument passing by value
-[n]private ? default private accessibility
-refer ? specify .NET assembly reference file name
-[n]swm ? specify individual warning message(s) to suppress
-verbose ? display verbose information
-version ? display version and owner information only
-[n]w ? display warnings
-[n]wide ? extended fixed source form line length
-winexe ? create .NET Windows executable
-[n]wo ? obsolescent feature warnings

• Processor
  450-megahertz (MHz) Pentium II-class processor,
  600-MHz Pentium III-class processor recommended
• Operating System
  Visual Studio .NET 2003 can be installed onto any of the following systems:
  • Microsoft Windows^© Server 2003
  • Windows XP Professional
  • Windows XP Home Edition (Limited functionality. Visual Studio .NET 2003 does not support creating ASP.NET Web applications or ASP.NET XML Web services when using Windows XP Home Edition.)
  • Windows 2000 Professional
  • Windows 2000 Server
• Memory
  • Windows Server 2003:
    160 megabytes (MB) of RAM
  • Windows XP Professional:
    160 MB of RAM
  • Windows XP Home Edition:
    96 MB of RAM
  • Windows 2000 Professional:
    96 MB of RAM
  • Windows 2000 Server:
    192 MB of RAM
• Hard Disk
  • 900 MB of available space required on system drive, 3.3 gigabytes (GB) of available space required on installation drive
  • Additional 1.9 GB of available space required for optional MSDN Library documentation
• Drive
  CD-ROM or DVD-ROM drive
• Display
  Super VGA (1024 x 768) or higher-resolution display with 256 colors
• Mouse
  Microsoft Mouse or compatible pointing device

To use Fortran for .NET without the Visual Studio .NET Fortran Integration:

• Processor
  • Client (a computer not working in a server capacity): 90-megahertz (MHz) Intel Pentium-class processor
  • Server (a computer working in a server capacity): 133-MHz Intel Pentium-class processor
• Operating System
  The Fortran for .NET and the .NET Framework 1.1 SDK can be installed on the following platforms:
  • Microsoft Windows^© Server 2003 family
  • Windows 2000, with the latest Windows service pack and critical updates available from the Microsoft Security Web site
  • Windows XP (Windows XP Professional is required to run ASP.NET)

• Memory
  • Client: 32 megabytes (MB) of RAM, 96 MB recommended
  • Server: 128 MB of RAM, 256 MB recommended
• Hard Disk
  660 MB of hard disk space required, 190 MB additional hard disk space required for installation (850 MB total)
• Display
  800 x 600 or higher-resolution display with 256 colors
• Input Device
  Microsoft mouse or compatible pointing device
• Other
  • Microsoft Internet Explorer 5.01 or later is required
  • Microsoft Data Access Components 2.6 is required for data scenarios (version 2.7 is recommended on a server)
  • Install the latest Windows service packs and critical updates from the Microsoft Windows Update site

What?	Why?
Mix Fortran and other .NET languages in the same application.	Libraries written in other languages exist. Use the right language for the right task.
Create Windows user interfaces by dragging and dropping buttons, data entry fields, check boxes, and more.	Reduce development costs. You want more than a command-line interface.
Create web forms using the same technique.	You want to make your application and its professional user interface available to the world over the Internet.
Create reusable custom controls, with Fortran, that anyone can use in their Visual Studio environment.	You know Fortran, you've created custom controls for one application, why not reuse those controls? Reduce development costs.
Create procedures that access or collect data that exist somewhere over the Internet. (XML Web service.)	Somebody else already did the work of collecting the information. Make it available, accessible. Offer a service.
Create applications that call procedures that access or collect that data.	Use the data that's available. You can reduce the time to obtain answers.
Create COM objects with Fortran.	You know Fortran. Use your Fortran procedures from other, non- .NET language programs.
Call, from Fortran, COM objects written in other languages.	You have access to any COM object that's ever been written.
Create applications that run wherever .NET has been implemented.	Microsoft's .NET Framework is based on open standards and will be implemented on other platforms.
Create libraries of useful functionality with Fortran (i.e., class libraries) that can be used and extended by any .NET language.	Don't limit your users to only those who know Fortran.
Easily call Windows APIs from Fortran.	You know Fortran and want to use the building blocks of Windows.
Code functionality into your web pages using Fortran.	You know Fortran. It's a way to add smarts to a web page.
Easily read from and write to databases. (ADO.NET - drag and drop database access.)	It's where you keep your data.