A good place to look for FAQ's is: rtfm.mit.edu, /pub/usenet
If you have comments/suggestions/edit proposals please send them to me ([email protected]). I do not promise to accept 'em. I encourage others to make better FAQ lists, so I can retire this one.
The structure of the current list has been modified from previous versions in an attempt to group related questions according to their topic, and to maintain consistency with the new order. Let the author know if any inconsistencies have been intorduced by the revision. William B. Clodius contributed the reorganization
1.1) The language(s) and its(their) development
1.1.0) How should one spell FORTRAN/Fortran?
FORTRAN is generally the preferred spelling for discussions of versions of the language prior to the current one ("90"). Fortran is the spelling chosen by X3J3 and WG5. In this document a feeble effort has been made to capitalize accordingly (e.g. vast existing software ... FORTRAN vs. generic Fortran to mean all versions of the standard, and specifically the modern dialect, ISO 1539:1991).
~From: [email protected] Walt Brainerd There was an effort to "standardize" on spelling of programming languages just after F77 became a standard. The rule: if you say the letters, it is all caps (APL); if you pronounce it as a word, it is not (Cobol, Fortran, Ada). See, for example the definitive article describing Fortran 77 in the Oct 1978 issue of the Comm. of the ACM. The timing was such that FORTRAN got put on the standard itself, though many always after that have referred to it as Fortran 77. Of course, there are those who think it is not truly Fortran if not written with all caps.
ed note
ISO 1539:1991 and its ANSI counterpart X3.198-1992
consistently employ the spelling "Fortran" to refer to the language
being defined. Reference(s) to the older version employ "small caps"
for the "ORTRAN" characters.
1.1.1) Where can I learn more about the history of Fortran?
~From: [email protected] (Michael Metcalf )
The history of Fortran is documented in:
Annals of History of Computing, 6, 1, January, 1984 (whole issue).
Programming Systems and Languages (S. Rosen ed.), McGraw Hill,
1967, pp 29-47 (this is Backus's original paper).
History of Prorammining Languages (R.L. Wexelblat ed.), Academic Press, 1981, pp 25-74.
A summary appears in vol. 5 of the Encyclopedia of Science and Technology, Academic Press, 1986, under 'Fortran'. and in Chapter 1 of Fortran 90 Explained (Oxford, 1990).
1.1.2) How does Fortran 90 relate to FORTRAN '77?
With a few minor exceptions, Fortran 90 is a superset of X3.9-1978 FORTRAN.
But this does not mean that all "77" codes will port sans changes. Many (if not most) programmers employed constructs beyond the '77 standard, or rely on unspecified behavior (say, assuming that an OPEN of an existing file will position the file pointer to just past the last record already written) which has changed (that is to say, has become specified).
This leads to the obvious question, what is new in Fortran 90?
A complete answer would require considerable text. Some of the most obvious additions are:
While it is always tricky to characterize the motives of a large group of people, I khb am inclined to try as follows:
1) array notation (operators, etc.)
2) dynamic memory allocation
3) derived types and operator overloading
4) keyword argument passing, INTENT (in, out, inout)
5) modules
6) modern control structures
7) free format source code form 8) other stuff
'90 incorporates two sets of improvements: (1) relatively minor fixups that *could* have been done earlier (2) relatively major changes to enable better software engineering practices.
Sometimes a "minor" fixup has major effect, such as addition of free form source form combined with canonization of the MIL-STD 1753 INCLUDE.
I further go off on a limb and assert that it was the goal of the *committee* to evolve Fortran in a fashion to enable it to continue to be the premier language for scientific computation.
Fortran 90 was adopted as an International Standard by ISO in July,
1991. It was published by them as ISO/IEC 1539:1991, and is
obtainable directly for 185 Swiss francs from
ISO Publications
1 rue de Varembe
Case postale 56
CH-1211 Geneva 20
Switzerland
Fax. + 41 22 734 10 79
or from:
American National Standards Institute
Attn: Customer Service
11 West
42nd Street
New York, NY 10036
Phone: (212)642-4900 8:45-4:45 (EST)
Fax: (212)302-1286
In accordance with an official agreement with the International
Standards Organization, Unicomp is now able to distribute electronic
versions of the Fortran 90 standard: "ISO/IEC 1539 : 1991, Information
technology--Programming languages--Fortran".
The money received from this effort will go partly to fund ISO activities and partly to recover the costs incurred by Unicomp in preparing and typesetting the standard document. The prices are set by ISO.
The document can be obtained in three versions:
1. An ASCII version suitable for viewing on a
computer terminal using any kind of editor. Cost: USD 125.
2. A PostScript version with a license allowing the purchaser to
print n paper copies. Cost: USD 125 + 10n.
3. Complete source in ditroff with macros and software to extract and create the annexes. The source constitutes a fairly high level marked-up document; for example, each program beginning and ending is marked and there are few low-level typographic commands such as size and font changes. Cost USD 1000.
I am quite enthused especially about version (2). If you want to have
10 copies for your organization, and it costs $10 to make a printed
copy, then the cost to make the 10 copies would be $125 + $200, or
just $32.50 per copy, which is a substantial savings over purchasing
paper copies.
Versions (1) and (3) will be accompanied by a license restricting use to one CPU and prohibiting copying, except for backup purposes, etc. The version (2) license will prohibit distributing any of the printed copies outside of the purchasing organization.
If you have special requirements, such as wanting to distribute a copy with each version of your compiler or using the source as a part of your documentation, we can make special arrangements, subject to the approval of the ISO. Please advise me of your requirements and we can work up a proposal together.
ISO and Unicomp think this will provide the oft requested access to the standard in electronic form. This is the first time this is being tried, so we hope that organizations will be careful to observe the rules and encourage the continued availability of this and other standards in electronic form.
Payment can be made by Visa or MasterCard, or with a check on a US Bank in US funds. We unicomp will accept a purchase order only if the amount is $500 or more.
Walter S. Brainerd; Unicomp; phone:
505-275-0800.
email: Walt Brainerd [email protected]
;;; Additional note. X3J3 working papers are often available via ftp.
ftp.ncsa.uiuc.edu, directory x3j3.
rpc wrote:
It has been a few years since I last ordered a MIL-STD, so my information might be out-of-date. At that time, the address to write for MIL-STDs was
Naval Publications and Forms Center, Code 3015
5801 Tabor Ave
Philadelphia, PA 19120
Phone: 1-(215)-697-4834
Use form DD1425, if possible (they will send you a copy with your first order).
MIL-STD 1753 is a short document (about 10 pages).
And finally, note that the FORTRAN 77 standard is online at the Fortran Market.
1.1.4) Who creates these silly standards anyway?
Typically X3J3. X3J3 is an ANSI subcommittee dedicated to Fortran. WG5 is the ISO counterpart. WG5 owns responsibility for Fortran on an international basis. WG5 has previously tasked X3J3 to do the work. This arrangement continues.
WG5 is composed of Fortran users, vendors, and academics from several ISO supporting nations. Delegates represent *their*countries* not their companies; so several delegates from a single company is permitted.
ANSI rules prohibit multiple voting delegates from the same company. X3J3 is composed of users (aerospace, government labs, military, DECUS, railroads, oil to name a few), vendors (IBM, CRI, Sun, Convex, DEC, UNISYS, to name a few) and the odd academic (oxford, yale, liverpool, to name a couple). Members need not be US citizens nor must their company be US domiciled. Being a member of a standards group is typically involves non-trivial work. To be effective, one should plan on at least 8 weeks of time per year (those who are really doing the hard work do far more). This time commitment is typically far more expensive than the travel and membership costs.
X3J3 meetings are open to the public. There are typically 4 meetings a year, typically 3 are in the US and 1 *may* be overseas (to precede or follow the WG5 plenary session). Membership fees are levied by ANSI, and are on the near order of $600 ($300ish cast as an ISO "tax", but mandatory for all). In addition, attendees to a particular X3J3 meeting pay a "meeting fee" which covers reproduction costs, snacks and etc. The meeting fee has been about $100 for the last several meetings.
WG5 has established various goals and targets for future work. Roughly speaking 5yrs rather than 13years are the targets for future work.
Current work projects include cleanup and interpretations of Fortran (90), features for future versions of the standard (e.g. parallel processing, "object-oriented" technologies, etc.). In addition to work done directly by X3J3, there is work on standardized modules, and OS bindings taking place in other organizations. X3J3 would like to keep track of such efforts, those involved are invited to inform X3J3 early in their development efforts if possible. X3J3 is currently working with X3H5, DIN (varying string character) and tracking the efforts of HPFF.
New members are always welcome. Visitors are also; though it is very hard to get a good grip on things in only one meeting!
Contact the X3J3 chair for more information:
Upcoming meeting is[email protected] chair
5 Feb - 9 Feb Las Vwgas
papers are often available via ftp. ftp.ncsa.uiuc.edu, directory x3j3.
On Fortran 90:
English:
Fortran 90 - Counihan, Pitman,
1991, ISBN 0-273-03073-6.
Fortran 90 Explained - Metcalf and Reid, Oxford University Press,
1990, ISBN 0-19-853772-7, about $30. This book is a complete, audited
description of the language in a more readable style than the standard
itself. It is kept up-to-date on each printing with X3J3 and WG5's
latest interpretations. It has seven Appendices, including an extended
example program that is available by ftp, and a comprehensive Index.
Fortran 90 for Scientists and Engineers - Brian D. Hahn, Edward Arnold, 1994, ISBN 0-340-60034-9.
Fortran 90 Handbook - Adams, Brainerd, Martin, Smith and Wagener, McGraw-Hill, 1992, ISBN 0-07-000406-4.
Fortran 90 Language Guide - Gehrke, Springer, London, 1995.
Fortran 90 Programming - Ellis, Philips, Lahey, Addison Wesley, Wokingham, 1994, ISBN 0-201-54446-6.
Migrating to Fortran 90 - James F. Kerrigan, O'Reilly Associates,
1993, ISBN 1-56592-049-X.
Programmer's Guide to Fortran 90, second edition - Brainerd, Goldberg and Adams, Unicomp, 1994.
Programming in Fortran 90 - Morgan and Schonfelder, Alfred Waller, Oxfordshire, 1993, ISBN 1-872474-06-3.
Programming in Fortran 90 - I.M. Smith, Wiley, ISBN 0471-94185-9.
Fortran 90, Loren P. Meissner (U. of San Francisco) (c) 1995, PWS Publishing Co., ISBN 0-534-93372-6
Chinese:
Programming Language FORTRAN 90 - He Xingui, Xu zuyuan, Wu gingbao
and Chen mingyuan, China Railway Publishing House, Beijing, ISBN
7-113-01788-6/TP.187, 1994.
Dutch:
Fortran 90 - W.S. Brainerd, Ch.H. Goldberg, and J.C. Adams, translated by J.M. den Haan, Academic Service, 1991, ISBN 90 6233 722 8.
French:
Fortran 90; Approche par la Pratique - Lignelet, Se'rie Informatique E'ditions, Menton, 1993, ISBN 2-090615-01-4.
Fortran 90. Les concepts fondamentaux, the translation of "Fortran
90 Explained" M. Metcalf, J. Reid, translated by M. Caillet and
B. Pichon, AFNOR, Paris, ISBN 2-12-486513-7.
Fortran 90; Initiation a` partir du Fortran 77 - Aberti, Se'rie Informatique E'ditions, Menton, 1992, ISBN 2-090615-00-6.
Les specificites du Fortran 90, DUBESSET, M. et VIGNES, J., editions Technip, 1993. ISBN 2-7108-0652-5
Manuel complet du langage Fortran 90, et guide d'application, LIGNELET, P., S.I. editions, Jan. 1995. ISBN 2-909615-02-2
Programmer en Fortran 90, DELANNOY, C., Eyrolles, 1992. ISBN 2-212-08723-3
Savez-vous parler Fortran, AIN, M., Bibliotheque des universites (de Boeck), 1994. ISBN 2-8041-1755-3
Support de cours Fortran 90 IDRIS - Corde, P. Delouis, H. (anonymous ftp:// ftp.ifremer.fr:pub/ifremer/fortran90/f90_cours_4.ps.gz).
German:
Fortran 90 - B.Wojcieszynski and R.Wojcieszynski, Addison-Wesley,
1993, ISBN 3-89319-600-5.
Fortran 90: eine informelle Einf"hrung - Heisterkamp, BI-Wissenschaftsverlag, 1991, ISBN 3-411153-21-0.
Fortran 90, Lehr- und Arbeitsbuch fuer das erfolgreiche Programmieren - W.S. Brainerd, C.H. Goldberg, and J.C. Adams, translated by Peter Thomas and Klaus G. Paul, R. Olbenbourg Verlag, Muenchen, 1994, ISBN 3-486-22102-7.
Fortran 90 Lehr- und Handbuch - T. Michel, BI-Wissenschaftsverlag,
1994.
Fortran 90 Referenz-Handbuch: der neue Fortran-Standard - Gehrke, Carl Hansen Verlag, 1991, ISBN 3-446163-21-2.
Programmierung in Fortran 90 - Schobert, Oldenburg, 1991.
Software Entwicklung in Fortran 90 - U"berhuber and Meditz, Springer Verlag, 1993, ISBN 0-387-82450-2.
Japanese:
Fortran 90 Explained - Metcalf and Reid, translated by H. Nisimura, H. Wada, K. Nishimura, M. Takata, Kyoritsu Shuppan Co., Ltd., 1993, ISSN 0385-6984.
On Fortran in general:
Author Title Year Kruger Efficient Fortran Programming 1990 Mojena/Ageloff FORTRAN 77 1990 Boyle FORTRAN 77 PDQ 1989 Bezner FORTRAN 77 1989 Tremblay PROGRAMMING IN FORTRAN 77 1988 Salmon ENGINEERS SCIENTISTS WITH FORTRAN 77 1988 Nyhoff/Leestma FORTRAN 77 FOR ENGINEERS SCIENTISTS 1988 McCracken/Salmon ENGINEERS SCIENTISTS WITH FORTRAN 77 1988 Davis/Hoffman FORTRAN 77: A STRUCTURED DISCIPLINED STYLE 1988 Barnard/Skillicorn FORTRAN 77 FOR ENGINEERS AND SCIENTISTS 1988 Gregory A. Moses Engineering Applications Software Develop..1988 Mashaw PROGRAMMING STRUCTURED FORTRAN 77 1987 Cole FORTRAN 77: A STRUCTURED ... APPROACH 1987 Boillot UNDERSTANDING FORTRAN-77 1987 Starkey/Ross FUNDAMENTAL PROGRAMMING WITH FORTRAN 77 1986 Rouse/Bugnitz INTRODUCTION TO FORTRAN 77 1986 Ratzer FORTRAN 77 COURSE 1986 Page FORTRAN 77 FOR HUMANS 1986 Lehman SOCIAL SCIENCES: ALGORITHMS FORTRAN 77 1986 Smith FORTRAN 77: A PROBLEM-SOLVING APPROACH 1985 Shelly FORTRAN 77: AN INTRODUCTION 1985 Nickerson FUNDAMENTALS OF FORTRAN 77 PROGRAMMING 1985 Metcalf EFFECTIVE FORTRAN 77 1985 Metcalf FORTRAN Optimization 1985 McKeown STRUCTURED PROGRAMMING USING FORTRAN 77 1985 Hume FORTRAN 77 FOR SCIENTISTS ENGINEERS 1985 Dillman PROBLEM SOLVING WITH FORTRAN 77 1985 Brainerd FORTRAN 77 FUNDAMENTALS AND STYLE 1985 Borse FORTRAN 77NUMERICAL METHODS FOR ENGINEERS 1985 Adman FORTRAN 77 SOLUTIONS NON-SCIENTIFIC PROBS. 1985 Etter PROBLEM SOLVING WITH STRUCTURED FORTRAN 77 1984 Etter PROBLEM SOLVING USING FORTRAN 77 ? Dyck FORTRAN 77: A STRUCTURED APPROACH ... 1984 Chivers/Clark FORTRAN 77: A HANDS ON APPROACH 1984 Adman FORTRAN 77 FOR NON-SCIENTISTS 1984 Willamson/Levesque A GUIDEBOOK TO FORTRAN ON SUPERCOMPUTER 1989 Rule FORTRAN 77: A PRACTICAL APPROACH 1983 Rouse/Bugnitz PROGRAMMING THE IBM PC: FORTRAN 77 1983 Nyhoff/Leestma PROBLEM SOLVING WITH FORTRAN 77 1983 Marateck FORTRAN 77 1983 Lehmnkuhl FORTRAN 77 1983 Law ANSI FORTRAN 77: INTRO. TO SOFTWARE DESIGN 1983 Holoien/Behforooz ... STRUCTURED PROGRAMMING WITH FORTRAN 77 1983 Grout FUNDAMENTAL..PROGRAMMING USING FORTRAN 77 1983 Fleming/Redish THE U. S. MC MASTER GLOSSARY OF FORTRAN-77 1983 Cole ANSI FORTRAN IV WITH FORTRAN 77 EXTENSIONS 1983 Wu ANSI FORTRAN IV 77 AND BUSINESS PROGRAMS 1982 Pollack STRUCTURED FORTRAN 77 PROGRAMMING 1982 Katzan FORTRAN 77 1982 Gibson/Young INTRO TO PROGRAMMING USING FORTRAN 77 1982 Ellis STRUCTURED APPROACH FORTRAN 77 PROGRAMMING 1982 Durgin FORTRAN 77 1982 Nanney A PROBLEM-SOLVING APPROACH USING FORTRAN77 1981 Merchant FORTRAN 77: LANGUAGE AND STYLE 1981 Khailany BUSINESS PROGRAMMING FORTRAN IV/ANSI F.. 1981 Ashcroft PROGRAMMING WITH FORTRAN 77 1981 Wagener FORTRAN 77 ? Wagener PRINCIPLES OF FORTRAN 77 PROGRAMMING 1980 Meissner/Organick FORTRAN77 FEATURING STRUCTURED PROGRAMMING 1980 Hume/Holt PROGRAMMING FORTRAN 77 1979 Balfour PROGRAMMING IN STANDARD FORTRAN 77 1979
Copyright but freely available course material is available from Manchester Computer Centre on the World Wide Web with the URL:
http://www.hpctec.mcc.ac.uk/hpctec/courses/Fortran90/F90course.html The ftp address is ftp.mcc.ac.uk, in the directory /pub/mantec/Fortran90.
A complete Tutorial is available under WWW with the URL
http://asis01.cern.ch/CN/CNTUT/f90/Overview.html
or via anonymous ftp from
cernvm.cern.ch in the directory cnl.200 and as the file f90tutor.ps.
An ASCII copy of this material as a set of slides for a six-hour course is available from [email protected].
Courses are available from:
Walt Brainerd, a member of X3J3, also on HPF ([email protected]);
PSR (see above);
CETech, Inc. (also on HPF)
8196 SW Hall Blvd., Ste. 304,
Beaverton, Oregon 97008, USA.
Phone: (503)644-6106 Fax: (503)643-8425
([email protected]).
Some European companies offering courses and conversion consultancy are:
IT Independent Training Limited, 113 Liscombe, Birch Hill, Bracknell, Berkshire, RG12 7DE, UK
tel. +44 344 860172 fax. +44 344 867992
Simulog, attn. Mr. E.Plestan,
1 rue James Joule, F-78286 Guyancourt Cedex, France
tel: +33 1 30 12 27 00 fax: +33 1 30 12 27 27
CTS, Prinz-Otto Str. 7c, D-85521 Ottobrunn , Germany tel: +49-89-6083758 fax: +49-89-6083758
1.2.3) What constitutes good FORTRAN style?
One rendition of a FORTRAN 77 style guide is available through anonymous ftp from ics.uci.edu (128.195.1.1). To retrieve (please note that it's not really "anonymous", that's just the Name that you'll be using):
% ftp ics.uci.edu anonymous enter your e-mail address at Password: prompt cd pub/levine ascii get F77_Style_Guide bye
If you can't access this site directly, please send an e-mail request to [email protected] (BITNET: levine@uci, UUCP: ...!uunet!ucivax!levine).
1.3) General Fortran (particularly Fortran 90) resources
Updated version :
Note that my F90 FAQ (Q36 of the Fortran FAQ) is available on the WWW at URLs
ftp://ftp.ifremer.fr/ifremer/ditigo/fortran90/engfaq
http://scg.ex.a c.uk/people/eggen/Fortran90/f90-faq.html http://lenti.med.umn.edu/~mwd/f90-f aq.html http://www.uni-karlsruhe.de/Uni/RZ/Software/Anwendungen/LANG/F90/ola gnon-faq.html http://www.ifremer.fr/ditigo/molagnon/fortran90/engfaq.html
F90 FAN's : Fortran 90 Frequently Asked about News. A Fortran 90 addition to the Fortran FAQ.
Michel Olagnon - October 1st, 1993. Last updated - June 30th, 1995.
Send flames and suggestions for improvement to [email protected]
The current updated version of this FAQ is available as
ftp://ftp.ifremer.fr/ifremer/ditigo/fortran90/engfaq
It is also on the www at URLs: http://www.ifremer.fr/ditigo/molagnon/fortran90/engfaq.html (France) http://www.uni-karlsruhe.de/~Fortran90/olagnon-faq.html (D)
http://scg.ex.ac.uk/people/eggen/Fortran90/f90-faq.html (UK) http://lenti.med.umn.edu/~mwd/f90-faq.html (USA)Contents :
1.- Fortran 90 and Fortran 77
2.- Available in Fortran 90:
| Compilers Code re-structurers and converters
| Libraries and utilities
Tests and Benchmarks
Examples and repositories
Courses and Consultancy
3.-
Documentation:
Standards
Journals
Tutorials and other
documents
Books
Articles
Other places for help on
Fortran 90
4.- Fortran 90 Benchmarking
5.- Announced, foreseen, and
rumours
6.- Workshops, seminars, conferences
7.- Developments,
related languages
Standard
HPF
PVM
Parallel
Programming
8.- Addresses
1.- Fortran 90 and Fortran 77:
Fortran 90 is, with very few exceptions, a superset of Fortran 77. The FAQ of the Usenet group Comp.lang.fortran deals with both standards, and may be obtained, like any FAQ, via anonymous ftp from rtfm.mit.edu, directory /pub/usenet. It is also available on the WWW http://www.cis.ohio-state.edu/hypertext/faq/usenet/fortran-faq/faq.html
The present document is an attempt to supplement that FAQ with some specific Fortran 90 information. Anyone interested is also invited to join the mailbase list comp-fortran-90, by sending an e-mail message to [email protected], containing as the only line: join comp-fortran-90 firstname lastname
The main extensions of Fortran 90 over Fortran 77 are: * array notation (for instance, X(1:N)=R(1:N)*COS(A(1:N))) * dynamic memory allocation (ALLOCATE, DEALLOCATE, ...) * derived types and operator overloading * better declarations, and prototyping possible * MODULES, allowing users to create ``storage pools'', or to define environment * more of modern control structures (SELECT CASE, EXIT, ...) * more of useful intrinsics (date, precision, arrays, ...) * free format source code form
``Pure'' Fortran 77 is F90 compatible. Yet, it is better to convert it to a ``mixed'' format, acceptable both as free and fixed source form Fortran 90, which only requires replacing C by ! as the comment character, to use as the continuation line character, and to append it to the continued line, to remove blanks embedded inside constants or identifiers, and to check some intrinsics usage. Most of this can be done automatically.
Fortran 90 allows the Fortran 77 programmer to write code faster, to
make it more legible, and to avoid many bugs. For a newcomer to
programming, it is an opportunity to learn a modern language, with
most recommended features, and yet to be in line with scientific and
industrial engineering communities where Fortran is and is going to
remain for a good while THE favourite language.
2.- Available in Fortran 90:
Compilers --------- Please note that none of the following is free. There is presently no free F90 compiler, only a verifier by Nag that does not generate executable code.
Apogee - optimized for SPARC architectures, Meiko CS-2HA.
CRAY CF90 - for Crays YMP and YMP-C90, Superserver 6400
and Sparc Solaris 2.3, plans for HP, SGI
DEC Fortran 90 V1.1 - for DEC OSF/1 AXP, including HPF
extensions. for DEC OPENVMS AXP (june 1995)
EPC Fortran 90 - for Sparc Solaris 1.X and 2.X, IBM RS/6000,
Intel 3/486 (SVR34, Solaris 2.x), Motorola
88000/100/100 (SVR34)
Fujitsu - full compiler for Sparc Solaris 1.1 and 2.x
next: Sun Sparc (MP) 3Q/95, HP PA-RISC 4Q/95
MIPS ABI 4Q/95, Windows 1Q/96
IBM XLF V3 - full compiler for RISC System/6000
+ KAP preprocessor - from KAI, for AIX
V3.2 and V4.1
Lahey LF90 - for DOS
MicroWay - for DOS, OS/2,Unix
NA Software F90+ - for OS/2, DOS/Windows3.1, Windows NT, Sun
Cost-effective personal version for PC
NAG f90 - uses C as intermediate language
now at rel:2.1, includes HPF extensions
exists in Linux version.
Pacific Sierra VAST-90 - uses F77 as intermediate language, for
Unix, VMS and Convex.
Parasoft - uses F77 as intermediate language
PGI - f90/HPF compiler, for SGI.
Salford FTN90 - PC implementation of NAG f90, direct
generation of object code.
SPARCompiler Fortran 90 - Part of the SunSoft's "High Performance Workshop".
Stern C. S. CF90 - Cray-compatible for DEC OSF/1
NOTE: Some vendors, such as Convex on their machines, offer
a number of F90 extensions, for instance array syntax or
ALLOCATE instruction.
Code re-structurers and converters
LOFT90, by NA Software
FOREST-90, FORESYS, by Simulog or 3ip
FORGE Explorer 2.0, Distributed
and shared memory Parallelizer,
Applied Parallel Research, Inc.
NAGWare f90 tools, pretty-printer, declarations standardiser,
precision standardiser, names changer.
CONVERT, conversion to F90 free format, proposed by
Mike Metcalf via anonymous ftp on
jkr.cc.rl.ac.uk (130.246.8.23), file /pub/MandR/convert.f90.
ftof90.c, minimal F77 - F90 conversion, via anonymous ftp on ftp.ifremer.fr,
file ifremer/ditigo/fortran90/ftof90.c
f90ppr.f90, F90 pre-processor similar to cpp, via anonymous ftp on ftp.ifremer.fr, file
HPF mapper, for PVM or Parmacs, on Sun clusters: NA software.ifremer/ditigo/fortran90/moware-1.0.tar.gz
Libraries and utilities
Emacs free-format f90-mode, available from mailbase.ac.uk /pub/lists/comp-fortran-90/files/. Among the options one finds automaticmatching and completion of all end-blocks (for example, indenting a line starting with end, finds the corresponding if/do/module... and checks/fills in the right kind of block and a possible name), it has an automatic
fill-function which breaks a line and inserts -signs (two if inside a
string) when a line gets too long, different coloring for
different features which is updated with every indent of a
line The most common commands are available via a menu.
Performance Library - LAPACK, BLAS, FFTPACK, VFFTPACK et LINPACK
optimized for SPARC (Sun Performance Workshop).
NAG fl90, numerical and statistical library, SPARC, SGI,
DECstation, and IBM RISC System/6000.
NAG tool components (parser, semantic analyser, tree
modification library and tree flattener).
Cray LibSci(tm), numerical library for Crays and Sparc Solaris 2.3
MPFUN (Multiple Precision Floating Point Computation Package) by David W. Bailey, for Cray CF-90, http://www.nas.nasa.gov/RNR/software.html
IMSL library (Visual Numerics)
INTERACTER graphics library for Lahey LF90 and Salford FTN90, on 386/486/pentium + DOS Extenders (Int. Soft. Serv.) http://www.demon.co.uk/issltd/ +44 (0)1543 503611 Fax 44 (0)1543 574566 [email protected]
GINOMENU: a Fortran GUI programmable toolkit that creates either a MOTIF or MS-Windows emulation of a GUI and runs under either UNIX/VMS (using X-Windows) or DOS. Bradly Associates Ltd +44 (0) 1344 779381 fax: +44 (0) 1344 773168 [email protected] http://www.bradassoc.co.uk/
Syntax verifier extracted from NAG compiler (version 2.1), put into public domain by NAG for Sun 3, Sun 4, Sgi, RS/6000,DECstation, Solaris and Linux.
Interactive checking of user's code
over www at
http://www.nag.co.uk:70/0/Forms/f90_interface.html
Lahey has F90 components (manual, array intrinsics, front end,...)
that they would like to license to others.
ISAM/VSAM/btree file structure, and Positional Key file structure
ISF and PKF modules, shareware from Garnatz and Grovender.
http://www.winternet.com/~gginc ,
ftp://ftp.winternet.com/users/gginc
CADNA, by professeur Vignes from Universite Pierre et Marie Curie, implements stochastic arithmetic in Fortran 90, and enables monitoring of precision loss and/or numerical instabilities during execution. (Control of Accuracy and Debugging for Numerical Aplications in Fortran)
More information available from AERO (see also articles by J. Vignes), or Pr. Chesneaux ([email protected]).
ISO/IEC 1539-2 - Variable length character strings in Fortran (with a demonstration of implementation)LAPACK, (minimaly) translated by myself (metcalf?), successfully passed all its tests with NAg-f90 2.0. I aggressively translated single precision Blas, and intend to do the same with other Blas as soon as I have time. Steve Moulton works on LAPACK conversion.
Tests and Benchmarks
NAGware Test suite - tests for compilers (same as: U_F90_TS Test suite - from Dr. Brian Smith (University of New Mexico), marketed by Unicomp and NAG. Now at release 1.4
Lahey Test suite - F77 F90 (license agreement)
SHAPE Test suite - 3400 tests of array instructions,from Spackman Hendrickson, Inc.
Parasoft Test suite - 1500 tests for compilers
Quetzal Benchmark from John K. Prentice, via anonymous ftp on unmfys.unm.edu, in pub/quetzal.
Benchmark of Syracuse University, via anonymous ftp on
minerva.npac.syr.edu, in /benchmark.
Channel benchmark by John D. McCalpin, via anonymous ftp on
perelandra.cms.udel.edu, in bench/channel.
Examples and repositories
Nag has set up a public repository for contributed code: WWW: http://www.nag.co.uk:70/1h/nagware/Examples
The Fortran Market has established itself on the World Wide Web. "ONE place to find all information, products, and services related to Fortran" WWW: http://www.fortran.com/fortran/market.html
Lahey Computer Systems is planning to set up an FTP'able site for
F90 modules - a kind of clearing house for public domain code. More
info soon !
11 000 lines offered by Richard Maine via anonymous ftp on ftp.dfrf.nasa.gov (130.134.64.17), file pub/fdas/f90sample/fdas.tar.Z
STEJOI, statistical package for joint occurrence events, on Sun, including source code and everything, via anonymous ftp on ftp.ifremer.fr, file ifremer/ditigo/fortran90/f90dvl.tar.gz.
Module unsigned_32, for definition and use of unsigned 32 bits integers, also on ftp.ifremer.fr, file ifremer/ditigo/fortran90/unsi32.f90.gz.
f90split, experimental version, similar to Unix BSD fsplit, but for free source form, also on ftp.ifremer.fr, file ifremer/ditigo/fortran90/f90split.f90.gz.
Algorithm 999 by A.G. Buckley for unconstrained nonlinear minimization, on ftp.royalroads.ca, pub/software/bbuckley/alg999/source.
Courses and Consultancy
CTS, Germany
Unicomp, USA
Pacific-Sierra Research Corp., USA
CETech, Inc., USA
3.- Documentation:
Standards
ISO/IEC 1539:1991 (E) International Standard Information technology -
Programming langages - Fortran Somewhat expensive (CHF 210 ~ US$ 140!)
for instance, at ISO. Surprisingly enough, the identical, save for
foreword and acknowledgements, ANSI standard X3.198-1992 is even more
expensive. Walter S. Brainerd, Unicomp., offers: - for 125 US$, an
electronic ascii monouser version, - for 125 + 10n US$, an electronic
PostScript version, and the right to make n paper copies, - or for
1000 US$, an electronic ditroff monouser version.
Journals
Fortran Journal ISSN 1060-0221 Enquiries: Walt Brainerd [email protected] Subscriptions: Fortran Users Group / P.O. Box 4201 / Fullerton, CA 92634 (about $30/year individual, $100/year company, ~$50/$150 outside the USA, call 1 (714) 441 2022)
Fortran Forum edited by Loren Meissner [email protected]
Subscriptions: ACM membership services: [email protected]
10$ members, 20$ non members
Tutorials and other documents
P. Corde and H. Delouis, "Support de cours Fortran 90 IDRIS". This is a very complete reference (224 pp.), in French, for which the authors have agreed to give free access.
ftp://ftp.ifremer.fr/ifremer/ditigo/fortran90/IDRIS_F90_cours_4.ps.gz
Copyright but freely available course material is available from Manchester Computer Centre on the World Wide Web with the URL: http://www.hpctec.mcc.ac.uk/hpctec/courses/Fortran90/F90course.html The ftp address is ftp.mcc.ac.uk, in the directory /pub/mantec/Fortran90.
Bo Einarsson and Yurij Shokin have written a tutorial on the transition from Fortran 77 to Fortran 90, with the title "Fortran 90 for the Fortran 77 programmer" nsc.liu.se (130.236.100.5) pub/bibliotek/f77to90.txt
Michel Goossens has now installed a Fortran 90 tutorial on the World Wide Web (WWW) under the URL :
http://asis01.cern.ch/CN/CNTUT/f90/Overview.html There is no copyright on this material.
There is a Fortran (90) tutorial on the net that might be of some use
ftp://ftp.cs.unm.edu/pub/smith_quetzal/Fortran90_Tutorial/
See also:
ftp://ftp.th-darmstadt.de/pub/thd/fortran/f90/
Books in English,
Adams, Brainerd, Martin, Smith. Fortran Top 90 - Ninety Key Features of Fortran 90, Unicomp, Sept. 1994.
Adams, Brainerd, Martin, Smith, Wagener. Fortran 90 Handbook, McGraw-Hill, 1992. ISBN 0-07-000406-4
Brainerd, W., Goldberg, and Adams. Programmer's guide to Fortran 90,
2nd edition, Unicomp, 1994. ISBN 0-07-000248-7
Counihan. Fortran 90, Pitman, 1991. ISBN 0-273-03073-6
Ellis, T.M.R, Lahey, T. and Philips, I. Fortran 90 Programming, Addison Wesley, 1994 ISBN 0-201-54446-6
Gehrke, W Fortran 90 Language Guide, Springer-Verlag, 1995 ISBN
3-540-19926-8 Softcover $49.00
Hahn, B.D. Fortran 90 for Scientists and Engineers, Edward Arnold,
1994. ISBN 0-340-60034-9
Kerrigan, J. Migrating to Fortran 90, O'Reilly and Associates, 1993 (2nd ed. Sept.94) ISBN 1-56592-049-X
Charles H. Koelbel, David B. Loveman, Robert S. Schreiber, Guy
L. Stelle Jr., Mary E. Zosel High Performance Fortran Handbook, MIT
Press, 349 pages, 1994. ISBN 0-262-61094-9 $24.95 in paper back ISBN
0-262-11185-3 $45 for hard cover
Meissner, L. Fortran90, PWS Kent, Boston, 1995 ISBN 0-534-93372-6
Metcalf, M. and Reid, J. Fortran 90 Explained, Oxford University Press, 1992. ISBN 0-19-853772-7
Morgan and Schonfelder, Programming in Fortran 90, Alfred Waller Ltd.,
1993. ISBN 1-872474-06-3
Smith, I.M. Programming in Fortran 90, Wiley 0471-94185-9 * in French,
Aberti, C. Fortran 90: Initiation a partir du Fortran 77, S.I. editions, 1992. ISBN 2-909615-00-6
Ain, M. Savez-vous parler Fortran, Bibliotheque des universites (de Boeck), 1994. ISBN 2-8041-1755-3
Delannoy, C. Programmer en Fortran 90, Eyrolles, 1992. ISBN
2-212-08723-3
Dubesset, M. et Vignes, J. Les specificites du Fortran 90, editions Technip, 1993. ISBN 2-7108-0652-5
Lignelet, P. Fortran 90: Approche par la Pratique, S.I. editions,
1993. ISBN 2-909615-01-4
Lignelet, P. Manuel complet du langage Fortran 90, et guide d'application, S.I. editions, Jan. 1995. ISBN 2-909615-02-2
Metcalf, M. et Reid, J. (translated by M. Caillet and B. Pichon)
Fortran 90: Les concepts fondamentaux, AFNOR Editions, 1993. ISBN
2-12-486513-7
Olagnon, M. Traitement de donnees numeriques avec Fortran 90, S.I. editions, in press. ISBN 2-909615-03-0
* in Chinese,
He Xingui, Xu Zuyuan, Wu Gingbao and Chen Mingyuan Programming
Language FORTRAN 90, China Railway Publishing House, Beijing, ISBN
7-113-01788-6/TP.187, 1994.
* in German,
Brainerd, W.S., Goldberg Ch.H., Adams J.C., translated by Peter Thomas
and Klaus G. Paul Fortran 90, Lehr- und Arbeitsbuch fuer das
erfolgreiche Programmieren, R. Olbenbourg Verlag, Muenchen, 1994, ISBN
3-486-22102-7.
Gehrke. Fortran 90 Referenz-Handbuch, Carl Hansen Verlag, 1991. ISBN
3-446163-21-2
Heisterkamp. Fortran 90: Eine Informelle Einfuehrung, BI-Wissenschaftsverlag, 1991. ISBN 3-411153-21-0
Langer. Programmieren in Fortran, Springer Verlag, 1993. ISBN
0-387-82446-4
Michel, T. Fortran 90 Lehr- und Handbuch, BI-Wissenschaftsverlag,
1994.
Schobert, Oldenburg. Programmierung in Fortran 90, 1991.
Ueberhuber, C., Meditz, P. Software-Entwicklung in Fortran 90, Springer Verlag, 1993. ISBN 3-211-82450-2
Wojcieszynski, B, Wojcieszynski, R. Fortran 90 Programmieren mit dem neuen Standard, Addison-Wesley, 1993. ISBN 3-89319-600-5.
* in Dutch,
Brainerd, W.S., Goldberg Ch.H., Adams J.C., transl. by J.M. den Haan Fortran 90, Academic Service, 1991. ISBN 90 6233 722 8.
* in Swedish,
Blom, K. Fortran90 - en introduktion, Studentlitteratur, Lund, 1994. ISN 91-44-47881-X * in Russian,
Metcalf, Reid Fortran 90 Explained
* in Japanese
Metcalf, Reid (translated by H.Nisimura, H.Wada, K.Nishimura,
M.Takata) Fortran 90 Explained, Kyoritsu Shuppan Co., Ltd., 1993 ISSN
0385-6984.
Articles
Baker, S., Complying with Fortran90; How does the current crop of Fortran90 compilers measure up to the standard? -- Dr. Doff's Journal (Jan. 1995) p68-76
Bernheim, M., Fortran Mode d'emploi - Fortran 90 -- Intereditions (1991) 163-176
Brankin, R.W., Gladwell, I., A Fortran 90 Version of RKSUITE: An ODE Initial Value Solver, Annals of Numerical Mathematics, Vol 1, 1994, in press.
Buckley, A. G., Conversion to Fortran 90: A Case Study -- ACM TOMS Vol20 n 3 Sept.1994 308-353
Buckley, A. G., Algorithm 999: A Fortran 90 code for unconstrained non linear minimisation -- ACM TOMS Vol20 n 3 Sept.1994 354-372
(ftp.royalroads.ca:pub/software/bbuckley/alg999)
Chesneaux, J.M., Description d'utilisation du logiciel CADNA_F -- MASI
92.32 (1992) Institut Blaise Pascal, Paris
Corde, P., Girou, D., Fortran 90: la nouvelle norme -- Tribunix Dossiers calculateurs, Vol 8. No. 41 (1992) 12-17
Craig, C., Slishman G., Variants of Matrix Multiplication for Fortran90 SIGNUM Newsletter Vol 29 N 2 Apr. 1994 4-6
Delves L.M, Schonfelder J.L, Craven P. Fortran90; an Overview Oct.1993 IASC
Delves M, N.A Performance of Fortran90 Compilers Nov. 1994
Digital Corporation, Evolving from Fortran77
towards Fortran90, Fall Decus
1993, San Francisco
Dodson Z., A Fortran90 Tutorial Nov.1993
Du Croz, Jeremy J., Building Libraries with Fortran
90
Fortran Journal 4/5, Sep./Oct 1992
Du Croz, J. The Nag Fortran90 library Nagua 14 april 1994 Oxford
Gehrke, Fachwoerterliste
Englisch-Deutsch fuer Fortran 90,
SPR.F90 2, RRZN, 18 S.,
1995
( http://www.rrzn.uni-hannover.de/Umdrucke/SPR.F90.2.ps )
Gehrke,
Fortran 90-Syntax: Eisenbahnschienen-Diagramme,
SPR.F90 3, RRZN, 48 S.,
1994
( http://www.rrzn.uni-hannover.de/Umdrucke/SPR.F90.3.ps )
Glassy, L.,
Tiny-Ninety: A subset of F90 for beginning programmers --
Fortran Journal
4/3, May/Jun. 1992, 2-6
Hanson, R.J., A design of high-performance Fortran
90 Libraries --
IMSL technical report series No. 9201 (1992)
Hanson, R.J.,
Operator and Function Modules with FORTRAN90 VNI Technical
Report series No
9305
Hanson, R.J., Matrix multiplication in Fortran 90 using Strassen's algorithm -- Fortran Journal 4/3, May/Jun. 1992, 6-7
Hennecke, M., A Fortran 90 interface to random Number Generation -- Computer Physics Communications, in press
Iles, Robert, Fortran 90: The First Two Years -- Unicom Seminar on Fortran and C in Scientific Computing, 1993.
Iles, R.,
Palant, L., Fortran 90: 2 ans deja -- Tribunix No. 49
Mai/Juin 1993,
32-37.
Hann, R. Nagware Fortran90 tools Nagua 14 april 1994 Oxford
Hill J.M.D The high performance Fortran library in Fortran90: sorting -Technical Report LPA7/TR02.9408 The London parallel applications center August 1994 (revise 9/1/1995)
Joubert, A.W The high performance Fortran library in Fortran90: prefix and suffix scans-Technical Report LPA7/TR01.9408 The London parallel applications center August 1994
Kearfott, R.B Algorithm
737: INTLIB: A Portable Fortran77 Interval Standard-
Function Library ACM
TOMS Vol20 n% 4, Dec. 1994 447-459
Kearfott, R.B A Fortran 90 environment
for research and prototyping of
enclosure algorithms for canstrained and
unconstrained non linear equations
ACM TOMS Vol 21, 1 , Juin 1995
63-78
Lahey, T., Fortran 90 is coming ! -- Programmer's Journal, Mar/Apr
1991.
Lignelet, P., Fortran -- Les Techniques de l'ingenieur, H2120, Dec
1993.
Mc Calpin, John D. Optimization of Fortran90 array notation : A Case Study Jan. 1995 ( perelandra.cms.udel.edu:/models/Papers/f90.ps ) Internal report College of Marine Studies, Univ. of Delaware submitted to "Scientific Programming"
Maine, R., Review of NAG Fortran 90 translator -- Fortran Journal 3/6, Nov/dec 1991.
Marshall,A.C, Fortran 90 derived types, User defined operators, Modules and Object Oriented Facilities The University of Liverpool BCS seminar 1994 (12 Sep. 1992), 30-33
Metcalf, M., Recent progress in Fortran standardization -- Computer Physics Communications 57 (1989) 78-83.
Metcalf, M., Fortran 90 - A summary --
Int. Journal of modern Physics C,
Vol. 1, Nos. 23 (1990)
193-206.
Metcalf, M., A derived data type for data analysis -- Computers in Physics, Nov/Dec 1991, 599-604.
Metcalf, M., A first encounter with Fortran 90 -- Fortran Journal 4/1, Jan/Feb 1992, 2-7.
Metcalf, M., An
encounter with F90 -- Particle World 3/3 (1993),
130-134.
Metcalf, M.,
Fortran 90 Tutorial -- CERN Computer Newsletter,
Nos.
206/207/208/209/210/211 (1992-1993).
Metcalf, M., Using the f90 compiler as a software tool -- CERN Computer Newsletter, No. 209 (1992).
Metcalf,
M., Still programming after these years -- New Scientist,
(12 Sep. 1992),
30-33
Morgan, S., Fortran90 An outline of the ISO standard BCS seminar
1994
Olagnon, M., Experience with NagWare f90 -- Fortran Journal
4/6,
Nov/dec 1992, 2-5.
Olagnon, M., f90ppr A Fortran90 Pre-processor A Fortran 90 Pretty- printer Fortran Journal Vol 7 n2 Mar/Apr 1995 pp8-14
de Polignac, Christian, Du Fortran VAX au Fortran 90 -- Decus,
Paris,
7 Avril 1993.
de Polignac, Christian, Interfacing a Fortran77
multiple precision package
using Fortran90 -- Nagua, Oxford, 14 april
1994.
Prentice, John K., Fortran 90 benchmark results -- Fortran Journal
5/3,
May/June 1993.
Prentice, John K., Performance benchmarks for Fortran90 compilers- Mathematech Vol1 n1 1994, 66-73
Prentice, John K., Ameko, A.K., Performance benchmarks for selected Fortran90 compilers (to appear in Fortran Journal)
Reid, John, The Fortran 90 Standard -- Programming environments for high level scientific problem solving, Gaffney ed., IEEE Trans., North-Holland (1992), 343-348.
Reid, John, Fortran 90,
the language for scientific computing in the
1990s --Unicom Seminar on
Fortran and C in Scientific Computing, 1992
Reid, John, The advantages of Fortran 90 -- Computing 48, 219-238.
Reid, John. Fortran90: the future -- Nagua 14 april 1994 Oxford
de Roeck, Yann-Herve, Plessix, Rene-Edouard, Combining F90 and PVM to construct synthetic seismograms by ray-tracing -- proc. IEEE Oceans 94.
Robin, F., Fortran 90 et High Performance Fortran, Bulletin technique CEA, Oct. 1992, 3-7.
Sawyer, M., A summary of Fortran
90 -- EPCC-TN92-04, Univ. of Edinburgh,
(1992).
Schonfelder, J.L.,
Semantic extension possibilities in the proposed
new Fortran -- Software
practice and experience, Vol.19, (1989),
529-551.
Schonfelder, J.L., Morgan, J.S., Dynamic strings in Fortran 90 -- Software practice and experience, Vol.20(12), (1990), 1259-1271.
Schonfelder, J.L. High
Performance Fortran and Fortran95 -- University of Liverpool Nov.
1994
Scott, Kilpatrick and Maley The formal specification of abstract data types and their implementation in Fortran 90 Computer Physics Communications 84 (1994) 201-225.
Sipelstein, J.M., Blelloch, G.E., Collection-oriented languages -- Proceedings of the IEEE, Vol. 79, No. 4, (1991), 504-530.
Vignes, Jean, Vers un calcul scientifique fiable : l'arithmetique stochastique -- La Vie des Sciences, Comptes rendus, serie generale, tome 10, 1993, No 2, 81-101.
Vignes, Jean, A stochastic arithmetic for reliable scientific computation MATCOM 940 - Mathematics and Computers in Simulation 35 (1993) 233-261.
Walker, D.W., A Fortran 90 code for magnetohydrodynamics. Part I: banded convolution -- Oak Ridge National Lab. report TM-12032 (1992).
Walter, W., Fortran 90: Was bringt der neue Fortran-Standard fuer das numerische Programmieren ? -- Jahrbuch Ueberblicke Mathematik Vieweg, (1991) 151-174.
Walter W.V Fortran XSC: A portable Fortran90 module library for accurate and reliable scientific computing -- Computing Supplementum 9, 265-286
Wampler, K. Dean, The Object-Oriented programming Paradigm and Fortran programs -- Computers in Physics, Jul/Aug 1990, 385-394.
Ward, T. The world's first Fortran90 compiler. PROGRAM NOW March 1992, 67-69
Willhoft, Robert G., Comparison of
the functional Power of APL2 and
Fortran 90 -- APL Quote Quad,
1991
Fortran90 at NAS: Perceptions and plans RND-93-001 http://www.nas.nasa.gov/NAS/TechReports/
Other places for help
on Fortran
90
http://asis01.cern.ch/CN/CNTUT/f90/O verview.html Fortran 90 Tutorials http://www.fortran.com/fortran/u_gd.html Programmer's Guide to Fortran 90 http://www.fortran.com/fortran/market.html Fortran Market http://www.cis.ohio-state.edu/hypertext/faq/usenet/fortran-faq/faq.ht ml Fortran FAQ ftp://interval.usl.edu/pub/interval_math/www/kearfott.html
Fortran90 interface modules for INTLIB interval computations
submitted to TOMS by Kearfott ftp://ftp.cs.unm.edu/pub/smith-quetzal/Fortran90_Tutorial/
FTP-able fortran90 Tutorial from ftp.cs.unm.edu http://www.fortran.com/fortran/free.html Free Software http://www.fortran.com/fortran/u_iso1539.html How to get Fortran 90 Standard documentation http://cuiwww.unige.ch/OSG/Langlist/Free/free-toc.html
Free Compilers/tools List- At
Cern
http://www.cs.indiana.edu/inds/proglang.html
Programming
Languages research - At Indiana
University
http://www.cs.cmu.edu:8001/Web/computing.html
Other
languages - At CMU.
4.- Fortran 90 Benchmarking ###########################
An interesting article by John K. Prentice appeared in the May/June
93 issue of Fortran Journal. He also gave a new one in the Nov/Dec 94
issue.
I made some tests myself with LAPACK, and got a ratio of 10 between Sun f77 and Nag f90 2.0 when no source change was performed. With an aggressive rewriting, especially using array instructions and intrinsics, the ratio gets down to 2, which is also that of a f77 [sd]axpy to a C one.
On actual applications, this ratio seems to be much closer to 1, and even sometimes in favor of Fortran 90. On Sept. 7th, 1993, John wrote "I think there is in fact beginning to be a quite large body of evidence to suggest that most of the efficiency fears about F90 are unfounded."
For Nag f90 on workstations, the effect of the underlying C compiler (gcc, vendor, etc...) seems very limited (less than 4%).
With more recent F90 compilers, performance seems at least as good
and often better than with the corresponding F77 compiler, for old F77
code. For instance, Lahey reports improvement from 8.5 to 14.1 Mflops
with linpack on a pentium between EM/32 and their F90 compiler.
5.- Announced, foreseen, and rumours ####################################
Absoft beta version of CF90 summer 1995 for Power Mac.
No known time-scale EPC compiler for HP and Convex (no official date)
KAP pre-processor (SPARC F90 beta as of 09/94, SGI F90 1st quarter 95)
MicroSoft works on compiler for Windows NT 3.5 and Windows 95 Lahey
LF90 for Windows (1995) Numerical recipies Beta test 4/95 MATLAB
compatibility with PowerStationFortran 90 (1st quarter 96)
6.- Workshops, seminars, conferences
NAG Users Association conference95 - Bonn (Germany) 13-15 September
1995 - submitt abstracts to the Nagua committee [email protected]
7.- Developments, related languages
Standard
Work did not stop with the publication of the Fortran 90 standard. A new release is scheduled for 1996 (called 95), mainly devoted to clarifications, corrections and interpretations. A more important revision is scheduled for 2000 (or 2001 ? called F2k though C.Burley's F00 is a pleasant alternative). Documents related to the work of X3J3 can be found via anonymous ftp on ftp.ncsa.uiuc.edu, directory x3j3.
HPF
High Performance Fortran (HPF) is a language for programming
massively parallel architectures. It lets the user insert directives
for code and data distribution among the processors in the (Fortran
90) code. Electronic copies of HPF draft specification are available
by anonymous FTP from the following sources: Machine name File name
titan.cs.rice.edu public/HPFF/draft/hpf-v10-final.tar
titan.cs.rice.edu public/HPFF/draft/hpf-v10-final.tar.Z
titan.cs.rice.edu public/HPFF/draft/hpf-v10-final.ps titan.cs.rice.edu
public/HPFF/draft/hpf-v10-final.ps.Z think.com
public/HPFF/hpf-v10-final.ps.Z ftp.gmd.de
hpf-europe/hpf-v10-final.ps.Z theory.tc.cornell.edu
pub/hpf-v10-final.ps.Z minerva.npac.syr.edu public/hpf-v10-final.tar.Z
Other information sources http://www.liv.ac.uk/HPC/Infopage.html (Liverpool University - High Performance Computing Information) http://www.liv.ac.uk/HPC/HPCpage.html (Liverpool University- High Performance Computing Information) http://www.uni-karlsruhe.de/~HPF/ http://www.lpac.ac.uk/SEL-HPC /
PVM
Parallel Virtual Machine consists of a library and a run-time environment which allow the distribution of a program over a network of (even heterogeneous) computers. It works with Fortran 77, C and to some extent Fortran 90. One can refer to the article by Y-H de Roeck and R-E Plessix, and a set of example wrapper routines for the PVM calls is available as ftp://ftp.ifremer.fr/ifremer/ditigo/fortran90/pvm2f90.tar.gz
There is a usenet comp.parallel.pvm group, and the FAQ for it can be found via anonymous ftp on rtfm.mit.edu, /pub/usenet.
Parallel Programming
An interesting report can be obtained via anonymous ftp on
bulldog.wes.army.mil:/pub/report.ps.Z , for a large review of products
related to parallel systems programming.
8.- Addresses
3ip, 104, rue Castagnary, F-75015 Paris, France
tel: +33 1 48 56 23 33, fax: +33 1 48 56 23 44
Absoft, 2781 Bond Street Rochester Hills, MI 48309, USA tel: (810) 853-0050 , Fax: (810) 853-0108 [email protected]
ACE, Van Eeghenstraat 100, 1071 Gl Amsterdam, Netherlands tel: +31 20 6646416, fax: +31 20 6750389
AERO, Mr. Berthon, 3 av. de l'opera. F-75001 Paris, France tel: +33 1 44 55 30 80, fax: +33 1 40 15 95 54
AFNOR, Tour
Europe, Cedex 7, F-92049 Paris la Defense, France
tel: +33 1 42 91 55
55
ANSI, 1430 Broadway, New York, N.Y 10018
Apogee Software Inc., 1901
S.Bascom Ave., Suite 325, Campbell,
CA 95008-2207, USA
tel: (408)
369-9001, fax: (408) 369-9018, [email protected]
Applied Parallel Research, Inc., 550 Main St., Placerville, CA 95667 tel: (916) 621-1600, fax: (916) 621-0593, [email protected]
ftp://ftp.netcom.com/pub/forge/home.html
CETech, Inc., 8196 SW Hall Blvd.,
Ste. 304, Beaverton, Oregon 97008, USA.
tel: (503) 644-6106, fax: (503)
643-8425, [email protected]
CRAY Research, Inc., 655 Lone Oak Drive, Eagan, MN 55121 http://www.cray.com/ , [email protected]
CTS, Prinz-Otto Str. 7c, D-85521 Ottobrunn, Germany tel: +49 89 6083758, fax: +49 89 6083758
DEC http://www.digital.com/info.html , [email protected]
EPC, 17 Alva St, Edinburgh, EH2 4PH, United Kingdom
tel: +44-31-225-6262, fax: +44-31-225-6644, [email protected] EPC, 20 Victor Square, Scotts Valley, California 95066 tel: (408) 438-1851, fax: (408) 438-3510, [email protected]
Fortran Journal, P.O. Box 4201, Fullerton, CA
92634, USA
fax: (714) 441-2022
Fujitsu Open Systems Solutions, Inc.,
3055 Orchard Drive, San Jose,
CA 95134 USA
tel: (408) 456-7809, fax:
(408) 456-7050, [email protected]
ICHOR, 27 rue Linne, F-75005 Paris, France
tel: +33 1 43 37 02 02
IDRIS, B.P. 167, F-91403 Orsay Cedex, France
ISO,
1 rue de Varembe, Case postale 56, CH-1211 Geneve 20, Switzerland
fax:
+41 22 734 10 79
Interactive Software Services Ltd., 25 St Michaels Close,
Penkridge,
Stafford ST19 5AD, UK
tel: +44 1785 715588, fax: +44 1785
714913, [email protected]
IT Independent Training Limited, 113
Liscombe, Birch Hill, Bracknell,
Berkshire, RG12 7DE, UK
tel: +44 344
860172, fax: +44 344 867992
KAI (Kuck Associates), Champaign, IL USA
tel: (217) 356-2288, fax: (217) 356-5199, [email protected]
Lahey Computer
Systems, Inc., 865 Tahoe Blvd., P.O. Box 6091,
Incline Village, NV
89450, USA
tel: (702) 831-2500, fax: (702) 831-8123,
[email protected]
Microsoft [email protected]
Microway, Research
Park, Box 79, Kingston, MA 02364, USA
tel: (508) 746-7341, fax: (508)
746-4678, [email protected]
NA Software Ltd, Roscoe House, 62 Roscoe St., Liverpool L1 9DW, UK tel: +44 51 7094738, fax: +44 51 7095645, [email protected]
NAG Ltd., Wilkinson House, Jordan Hill Road, Oxford, OX2 8DR, UK tel: +44 1865 311744, fax: +44 1865 311755, [email protected] http://www.nag.co.uk:70/intro NAG Inc., 1400 Opus Place, Suite 200, Downers Grove, IL 60515-5702, USA tel: (708) 971-2345, fax: (708) 971-2346, [email protected] NAG GmbH., Schleissheimerstr. 5, D-85748 Garching, Germany tel: +49 89 3207395, fax: +49 89 3207396 NAG Office, Espace III, 62 Boulevard Frederic Arnaud, 09200 Saint Girons
(Toulouse, France)
NAG Users Association, PO Box 426, Oxford, OX2 8SD, UK
tel: +44 1865 311102, fax: +44 1865 310139, [email protected]
Pacific-Sierra Research Corp., 2901 28th Street, Santa Monica, CA 90405 tel: (310) 314-2300, fax: (310) 314-2323, [email protected]
ParaSoft Corporation, 2500 E. Foothill Blvd, Pasadena, CA
91107, USA
tel: (818) 792-9941, [email protected]
PGI, The Portland Group, 9150 S.W Pioneer Ct., Suite H Wilsonville, OR 97070 ,USA tel: (503) 682-2806, fax: (503) 682-2637 [email protected]
Quetzal Computational Associates, 3200 Carlisle
N.E., Albuquerque,
NM 87110-1664, USA
tel: (505) 889-4543, fax: (505)
889-4598, [email protected]
Salford Software, Adelphi House, Adelphi Street, Salford M3 6EN, UK tel: +44 61 8342148, fax: +44 61 8342454
S.I.
editions, 9 av. Prince Hereditaire Albert, MC-98000, Monaco
tel: +33 92
05 35 51, fax: +33 92 05 35 04
Simulog, 1 rue James Joule, F-78286 Guyancourt Cedex, France (Mr. E. Plestan) tel: +33 1 30 12 27 00, fax: +33 1 30 12 27 27
Spackman Hendrickson, Inc., 13708 Krestwood
Drive, Burnsville,
MN 55337, USA
tel: (612) 892-5847, fax: (612)
892-5844
Stern Computing Systems [email protected]
Unicom Seminars Ltd., Brunel Science Park, Cleveland Road, Uxbridge, Middlesex, UB8 3PH, UK tel: +44 895 256484, fax: +44 895 813095, [email protected]
Unicomp, Inc., 1874 San Bernardino Ave NE, Albuquerque, NM 87122, USA tel: (505) 275-0800, fax: (505) 856-1501, [email protected]
Visual Numerics, [email protected]
I am always pleased to receive informations. Thanks to all those who sent some to me, and that I can not cite all because I lost some of
their names and addresses :-) | Michel OLAGNON1.3.2) Fortran Market
~Subject: (SC22WG5.609) Fortran Market/WWW
I hope all of you will be pleased to learn that the Fortran Market has established itself on the World Wide Web. Our goal is nothing short of providing one place to find all information, products, and servicesrelated to Fortran. The URL is:
http://www.fortran.com/fortran/market.html
The Market is under construction (and probably always will be), but there is already some free software available (just some simple, but perhaps useful, things so far). There are pointers to other locations containing relevant information, so you now need to remember only one place to find it all. Much more information, particularly about products and servies will be available in the near future, but I thought you might want to have a Sneak Preview of what things will look like.
Come visit the Market and let me know what you think of it. Thanks. walt ;;;;;
2.1) Compilers and preprocessors
2.1.1) Where can I get a free (FORTRAN 77) compiler?
There are two such in wide distribution.
One such is f2c.
~From: [email protected] (Mark Maimone)
Since there have been several requests for a Fortran to C
translator in the past week, I'm reposting the announcement about f2c.
The short answer is you can get f2c by anonymous-ftp from
netlib.att.com in directory dist/f2c.
F2c was derived from the original UNIX operating system's f77(1), and the generated C follows f77's calling conventions; on some machines, the resulting object files are interchangeable with (and behave indistinguishably from) objects compiled by f77. The main "advantage" of f2c is that it converts ANSI standard Fortran 77 into C without manual intervention, at least when invoked by a suitable script or makefile (that may need to exercise an f2c option to ensure that COMMON blocks are defined just once). The main "problems" are that f2c does no code restructuring (e.g., gotos are preserved) and that Fortran I/O gets converted into a bunch of calls; thus the translated C code doesn't look too pretty, and in general one would need to maintain the Fortran rather than its translation into C. [F2c is not meant to displace the services of commercial vendors whose business is to convert Fortran into maintainable C.]
There is a plethora of options, many of which exist to support different compilation environments for the translated C (e.g., ANSI C or C++ compatibility, different type sizes, separate files for COMMON blocks to appease "smart" linkers). So far f2c (and f2c-generated source) has compiled successfully on many machines: Sun, Vax, IBMRT, Apollo, SGI, MIPS, and Cray to name a few.
F2c has been under test by the net community for over a year and has been verified on the NBS tests, several large math libraries, floating point tests, even code for laying cable on the ocean floor!
To find out about f2c, send the following E-mail message to netlib ([email protected] or research!netlib):
send index from f2c
Your message will be answered automatically (by a program -- see CACM vol. 30 #5 (May, 1987), pp. 403-407). You will receive a reply explaining how to automatically acquire f2c source (about 600K), f2c library source (130K), and supporting info (man page, etc). Or you can anonymous-FTP to research.att.com and look in directory dist/f2c at these files:
all.Z -- 250K compressed shar file for f2c f2c.ps.Z
24 page tech report describing f2c index -- general info about files
libf77.Z, libi77.Z -- compressed shar files for libraries
Careful! Anything free comes with no guarantee.
---
Mark Maimone phone: (412) 268 -
7698
Carnegie Mellon Computer Science email: [email protected]
cmcspt![email protected]
Notes: f2c accepts only fairly vanillaFORTRAN; vendor supplied f77's usually produce better quality code, and accept a wider variety of codes.
More about f2c from Judah Milgram
I recently asked about running f2c with djgpp. Turns out to be easy and together they make a good Fortran compiler for PC's. Here's a summary.
I started with f2c dated Nov. 1994 (netlib.att.com in netlib/f2c). djgpp was v. 1.12 (omnigate.clarkson.edu in pub/msdos/djgpp.)
Use the pre-compiled msdos f2c executable that comes with the f2c release. Compile the libraries with djgpp, making the changes listed below. They aren't necessarily the most sensible changes, but they worked for me. Write if you have a better idea.
Thanks to all net people who helped, especially Dr. James Lupo.
Judah Milgram [email protected]
libf77/makefile: change: CC = cc to: CC = gcc
comment out:
ld -r -x -o $*.xxx $*.o
mv $*.xxx
$*.o
libf77/s_paus.c:
change:
extern int getpid(void), isatty(int),
pause(void);
to:
extern int getpid(void), isatty(int);
#ifndef
_djgpp_std_h
extern int pause(void);
#endif
libi77/makefile: change: CC = cc to: CC = gcc
comment out:
ld -r -x -o $*.xxx $*.o
mv
$*.xxx $*.o
libi77/fio.h:
add to top of file:
#ifdef abs
#undef
abs
#endif
libi77/rawio.h:
comment out entire block:
#ifdef MSDOS
#include
"io.h"
#define close _close
#define creat _creat
#define open _open
#define
read _read
#define write _write
#endif
Easiest way to build libf2c.a is to go into the f2c/ directory and do:
ar r libf2c.a libf77/*.o libi77/*.o ranlib libf2c.a (If you do it this
way you can delete libf77/libf77.a and libi77/libi77.a) Then copy
libf2c.a into djgpp/lib and copy f2c.h into djgpp/include
And remember to run the executable with 'go32 foo'. Or, do 'coff2exe foo' to produce a .exe file which you can run in the usual manner.
f2c is quite free.
The FSF has a f77 front end integrated with the gcc back end.
"A mailing list exists for those interested in the Fortran front end for GCC. To subscribe, ask: `[email protected]'. Or try "finger -l [email protected]";
There is no FSF project to do a f90 front end. The author of the g77 front end is willing, if anyone will fund it.
From Bill Thorson [email protected]
GNU Fortran (g77) Copyright (C) 1995 Free Software Foundation, Inc.
GNU Fortran (g77) Version 0.5.13 is now available to the public for beta testing in the usual GNU locations. The distribution is named:
g77-*.tar.gz. Where the '*' is the current version number. g77 requires that you also have a recent distribution of gcc. This compiler currently builds and installs it's own version of the f2c libraries (libf2c.a).
See g77 documentation for list of features or bugs.
Most GNU software is packed using the GNU `gzip' compression program. Source code is available on most sites distributing GNU software.
For information on how to order GNU software on tape, floppy or cd-rom, or printed GNU manuals, check the file etc/ORDERS in the GNU Emacs distribution or in GNUinfo/ORDERS on prep, or e-mail a request to: [email protected]
Someone asked for a cheap MSDOS fortran compiler for students. The bcf77 by andreas koesterli has a student version, which costs nothing. The student version may not be used in any comercial enviroment and problems. Its a version that write a none standart object format and requires 640KB. If all input is in UPPERCASE, it supports full fortran 77 standart.
The site is ftp.uni-stuttgart.de, the compiler can be found in /pub/systems/pc/lang/fortran/compiler/bcf77.zip. It can be access via [email protected] for those of You without ftp.
PI at the User Help Desk Comp.Center U of Stuttgart, FRG 26 years to go ! EMail: [email protected] Phone: +49 711 685-4828 (aka Kurt Jaeger)
In article [email protected], [email protected] (Charles F Randall) writes: | Note that the .txt file for this NOT in English: | | BC-FORTRAN77 Version.b besteht aus Compiler, Linker, | Modulbibliothek und einem residenten Laufzeitsystem, das | u.a. einen einfachen Debugger enthaelt. Diese Version | laeuft auf einem MS-DOS Rechner mit 640kB RAM. Eine | Festplatte ist nicht erforderlich. Hiermit soll in | einfacher Weise ein Compiler fuer Programmierkurse | zur Verfuegung stehen. Dem kommt entgegen, dass | entsprechende Compiler fuer ATARI ST und AMIGA existieren. | | Anfragen nach Zusendung einer anderen oder neueren Version | werde ich nur noch beantworten, wenn DM 20.- (Schein oder | Scheck) Aufwandsentschaedigung (Diskette, Umschlag, Porto | und Zeit) beigefuegt sind. Ich versende ausschliesslich | 3 1/2 Zoll Disketten. | | Anybody willing to translate?
Here's a quick and dirty translation (i.e., I didn't look in my dictionary, so the sentences in [] are just rough translations)
BC-FORTRAN77 Version b consists of a compiler, linker, module library, and a resident runtime system that contains (among other things) a simple debugger. This version runs on a MS-DOS computer with 640KB RAM. A hard disk is not required. [The intent is to provide a compiler for programming courses in a simple manner. Similar compilers exist for the ATARI ST and the AMIGA.]
Requests for another or a newer version will only be answered if they are accompanied by DM 20.- (check or cash) to defray costs (diskette, envelope, postage, and time). I can only send 3 1/2 inch diskettes.
"BC-FORTRAN 1.3b, is a FORTRAN compiler from Germany. The
documentation is in German. Sample source code is included. The
compiler generates big, inefficient EXE programs and is offered only
because there are no other pd/shareware FORTRAN compilers available.
700K of disk space is required."
Chris Doyle [email protected]
Stuff to be posted starts below this line. Adjust header/newsgroup/etc as appropriate. Thanks!
~From: [email protected]
For those people who FTP this thing and want to be able to read the documentation, I have translated the README file into English and will let you have a copy of the translation upon request. Translation is about 400 lines long.
BCF77 (FORTRAN 77 compiler, written by Andre Koestli) distribution. This compiler/linker/run-time module and supporting files are available via anonymous FTP from "uni-stuttgart.de" as the file "/soft/pc/lang/fortran/compiler/bcf77.zip".
... There have been many complaints about bcf - but it is free. I recommend Lahey's Personal Fortran PF77L to those who have been disappointed with bcf. I believe it costs US$99.
Alan Miller, Quality Improvement Project
CSIRO
Division of Mathematics Statistics, Melbourne, Australia
Phone: +61 3
542-2266 Fax: +61 3 542-2474 E-mail: [email protected]
Mail: CSIRO
DMS, Private Bag 10, Rosebank MDC, Clayton, Vic. 3169,
Australia
2.1.2) What is the best (FORTRAN 77) compiler for a PC?
There are many products, some are quite good. Few are free.
f2c and gcc can be had for the PC environment. Popular ones are:
Lahey (very fast compilation; excellent reputation for support)
Watcom (touted for good optimization)
MicroWay (support for odd floating point units)
LPI (multi-platform support)
MicroSoft (various good hooks into windows and such) Absoft
(multi-platform support)
It is beyond the scope of a faq to provide a commercial endorsement.
2.1.3) What is the best Fortran for...
Such recommendations are, at best, personal opinions. I've khb tracked some of the discussions and it would appear that
a) For the mac, Language Systems 800-252-6479 (inside US and Canada) 703-478-0181 703-689-9593 (fax) 703-709-0134 (BBS) langsys (Applelink) langsys (America Online) [email protected] (Internet) Language Systems Corp. 100 Carpenter Drive Sterling, VA 20164 b) For the PC it is harder. Many like Lahey Lahey Computer Systems, Inc. 865 Tahoe Blvd. P.O. Box 6091 Incline Village, Nevada 89450 Phones: (800) 548-4778 (702) 831-2500 Fax: (702) 831-8123 BBS: (702) 831-8023. UUNET: Sales [email protected] Tech support [email protected] Good code generation, good diagnostics, fast compilation, and good support are often quoted as reasons why folks liked LCS.
Apogee's compiler for SPARC architectures ([email protected]). Used on the Meiko CS-2HA.
Cray Research has a native compiler that is being marketed by them and Visual Numerics for workstations, starting with Suns (solaris 2.3+) ([email protected]). Absoft will market a PC version (486, Pentium and Macintosh PowerPC) ([email protected]).
DEC has been shipping a native compiler, including HPF, from June
1994. It is for OSF/1 AXP, with OpenVMS AXP and probably Windows NT
AXP following. It has no plans for VAX systems.
Native compilers for Sun, RS/6000, SGI, MIPS and, soon, x86 are available from EPC ([email protected] or [email protected]).
Fujitsu is marketing a native Fortran 90 Workbench for Solaris 1.1 and
2.x. Contact Unicomp ([email protected]) or Fujitsu ([email protected]).
HP has stated its intention to integrate the EPC f90 compiler into their compilation system. Details have not yet been made clear.
IBM has been shipping its optimizing, native compiler for the RS/6000, xlf Version 3, as of 31 December, 1993.
Lahey has been shipping a native LF90 compiler for DOS since 29 August, 1994 ([email protected]). It is particularly well optimized on the Pentium.
Microsoft is working on a compiler, release date unknown, for Windows NT 3.5 and Windows 95 (Chicago) ([email protected]).
Microway NDP Fortran 90 for 386/486, Pentium and 860 is available (tel. (508) 746-7341).
A compiler is available for most unix platforms, VMS and PCs
(including Linux) from NAG ([email protected] or
[email protected]). This was the first f90 compiler, released in
1991. The current version is 2.1. For more information see:
http://www.nag.co.uk/1h/nagware.html
NA Software supplies Fortran 90 Plus on 386/486, SPARC and T800 and T9000 transputers ([email protected]). They also supply a F77 to f90 convertor, LOFT90, and HPF.
VAST/f90 from PSR ([email protected]) is a complete f90 compiler, including a vectorizer, for unix, VMS and Convex. PSR also supplies VAST/77to90 to convert FORTRAN 77 programs into Fortran 90 syntax.
A compiler from ParaSoft ([email protected]) is available.
PGI has released a subset Fortran 90/HPF compiler, in particular for SGI ([email protected]).
A PC version of the NAG compiler is also available from Salford Software ([email protected]). A Windows NT version is planned.
SofTech has a licence to sell its own versions of DEC's HPF/f90 compiler.
Stern Computing Systems offers CF90, a Cray-compatible compiler for use on DEC OSF/1 platforms ([email protected]).
Sun (to be precise, the Developer Products group of SunSoft) has announced a native f90 compiler. It is available as Performance Workshop for Fortran 90 includes the first release of SPARCompiler Fortran 90 based on the CF90 product from Cray. Also included is SunSoft Performance Library (tuned versions BLAS[123] LAPACK, FFTPACK, VFFTPACK, licensed from DSS), and the usual programming environment addons (debugger, performance analyzer, group source code management etc.). f77 and C compilers are also provided in the Performance Workshop. The f90 component is adapted from the Cray f90 product. 30 day free demos available. For more information see http://www.sun.com/sunsoft/Products/Developer-products .
Other useful tools, like FORGE90 from APR ([email protected]), are available. A source form convertor, convert.f90, is obtainable by ftp from jkr.cc.rl.ac.uk in the directory /pub/MandR.
Both NAG and IMSL (now Visual Numerics, [email protected]) are beginning to offer f90 versions of their maths libraries that take full advantage of the language's library building capabilities. NAG contact info: NAG FL90 from [email protected], [email protected] and http://www.nag.co.uk/1h/numeric .
2.1.5) Tell me about Parallel Fortran dialects, what are they,etc.
~From: [email protected] (Larry Meadows)
[email protected] (Steve Spencer) writes:
We are trying to decide what parallel FORTRAN environment to port to a MIMD multiprocessor that we are building for ARPA. We are looking for information on the follwing environments:
FORTRAN90
HPF (High Performance
FORTRAN from Rice U. I think)
FORTRAN D
PVM (works with
F77 to provide a parallel env.)
Does anyone know where we can get information on the above
programming environments or any others that may be appropriate?
Fortran90 is an ANSI and an ISO standard. The usual reference is Fortran 90 Handbook, published by McGraw Hill. Several vendors provide Fortran 90 translators and/or compilers.
HPF
High Performance Fortran (HPF) is a language for programming
massively parallel architectures. It lets the user insert directives
for code and data distribution among the processors in the (Fortran
90) code.
Electronic copies of HPF draft specification are available by anonymous FTP from the
following sources: Machine name File name titan.cs.rice.edu public/HPFF/draft/hpf-v10-final.tar titan.cs.rice.edu public/HPFF/draft/hpf-v10-final.tar.Z titan.cs.rice.edu public/HPFF/draft/hpf-v10-final.ps titan.cs.rice.edu public/HPFF/draft/hpf-v10-final.ps.Z think.com public/HPFF/hpf-v10-final.ps.Z ftp.gmd.de hpf-europe/hpf-v10-final.ps.Z theory.tc.cornell.edu pub/hpf-v10-final.ps.Z minerva.npac.syr.edu public/hpf-v10-final.tar.ZFortran D is a precursor to HPF; as a commercial product it has been superceded by HPF, but several academic projects still exist that target Fortran D.
PVM is a message passing library and run-time environment; as such, it exists at a lower level than the previous items. One might imagine an HPF processor that produced FORTRAN77 with calls to PVM. There is a newsgroup on PVM. It is available through netlib, and possibly from Oak Ridge as well.
Hope this helps.
Larry Meadows The Portland Group
[email protected]
From:
[email protected]
Keith,
Here is a suggestion for your "Parallel Fortran dialects" question (Q30) (2.1.5) on your (very useful) Fortran FAQ. Larry Meadows' information on HPF is largely correct (except for his saying "massively" parallel--massively parallel is the one major parallel architecture for which HPF is not yet available), but I thought I'd contribute a few words about compiler availability:
High Performance Fortran (HPF) is an extended version of Fortran
90 for parallel programming. It lets the user insert directives into
Fortran 90 code which specify the distribution of data across
processors.
Currently, most HPF products are not true compilers, but source-to- source translators. Source-to-source translators are pre-processors that translate HPF code so that it can be compiled by a compiler without native HPF capability. They typically output FORTRAN77 source code, with calls to a message-passing library such as PVM or MPI.
Compilers, on the other hand, produce object modules containing calls to either a standard message-passing library like PVM or MPI (as in the PREPARE compiler currently under development in Europe), or to a customized message-passing environment (as in Digital's HPF compiler).
As of May, 1995, the following vendors offered HPF products:
Compilers Source-to-Source Translators
*Digital
Applied Parallel Research
Hitachi
Intel
Kuck and Associates
Meiko
Motorola
NA Software
NEC
Pacific Sierra Research
*PGI
SofTech
The first versions of HPF offered a partial implementation known as "Subset HPF". Beginning in 1995, a small number of vendors began offering implementations of the full HPF specification. Currently, only the vendors marked with an asterisk (*) offer full HPF support; all the others support Subset HPF.
The runtime performance of HPF codes varies widely from vendor to
vendor. The best-performing HPF products achieve performance
comparable to hand-optimized PVM code.
2.2) Other tools (pretty printers, lints, etc.)
2.2.1) I have heard of fortran "lints" what are they, and where can I get one?
Fortran compilers are not required (and most do not) to protect users from themselves, that is to say
Is non-standard complying but the compiler need not tell you about it. Arguably worse, the compiler can produce any result it deems fit, up to and including the start of world war III (assuming the right optional hardware has been installed).call sub(1) ... subroutine sub(i) i=i+10 return end
Fortran lint programs focus on searching out programming errors (or likely errors) and alerting the user.
There are a wide variety of commercial and pd products. A partial list follows:
IPT FORTRAN lint 1096 East Meadow Circle, Palo Alto, CA 94303, 415/494-7500.
Forwarn from quibus 719 527 1384.
QA-FORTRAN from PRL Programming Research Ltd
E-mail: [email protected]
Glenbrook House 1/11 Molesey Road Hersham Surrey, KT12 4RH Tel: 0932 88 80 80 Fax: 0932 88 80 81
FORCHECK from Leiden University ND 31 71 276804 "Announcing: The
demo of FORCHECK a Fortran development tool.
The MS-Windows (or WABI) based demo of FORCHECK, a Fortran
development tool, is now available simtel as
pub/msdos/fortran/fckdemo1.zip (SimTel Software Repository
(primary site oak.oakland.edu).
(Note: directory names, such as SimTel, are case sensitive.)
If you are a Fortran programmer it will be a great asset in developing portable and reliable code.
Leiden University
email: [email protected]
" end quote
Actually contrary to the posters claim, this isn't a demo, its a
hypertext file. Useful, helpful, but not a demo in the usual sense of
the word ; khb
FTNCHEK from netlib. One may receive FTNCHEK by mailing to
[email protected] the following message:
And Ajay Shah, (213)749-8133, [email protected] You may want to mention f2c followed by an ANSI C compiler as a great free fortran lint. I could not have survived writing fortran if it were not for f2c. You need to know some C to deal with the error messages, but that's not a bad price to pay.send ftnchek from fortran
HP provides a syntax checking facility with their Fortran 77 product.
Sun provides a syntax checking facility (triggered by Xlist) with their Fortran 77 product (3.0.1 and beyond).
Other vendors do too, no doubt.
~From: [email protected] (Ata Etemadi)... A very kind soul who
wishes to remain anonymous sent me the answer below. ...
1. There is a prettyprinter (called TIDY) available via FTP from the SimTel Software Repository (primary site oak.oakland.edu). It's in the directory SimTel/msdos/fortran (Note: the directory name SimTel is case sensitive.)
Capsule review: does an ok job, sometimes has trouble with newer
extensions (and even some Fortran 77 standard features). Not too
bright about making good continuation-line break decisions. Free, and
available via FTP, so probably the quickest solution. Includes source
(in Fortran).
2. Greg Flint ([email protected]) at Purdue distributes a
program called CLEAN77. Pretty good (higher quality than #1 above),
also free, but must be obtained from Purdue (not available via FTP,
not redistributable). Available for assorted systems: PC, UNIX, etc.
In Fortran, comes with source.
3. There is an excellent prettyprinter in TOOLPACK - probably has
more options than any other. Has trouble with extensions, such as
long variable names. Free, comes in source form, in Fortran.
TOOLPACK as a whole is pretty huge, and requires some work to install,
but it might be worth it if you stick to pretty much standard Fortran.
Distributed commercially for a fee by NAG, who may have a new,
improved version that is better than the free one - I don't really
know. Available via ftp (see archie for locations)
4. SPAG, formerly sold by OTG Systems (about $1000 for MS-DOS, more for Unix). Its main function is to restructure GOTOs into IF-THEN-ELSEs, but it also prettyprints. (I think they renamed this within the past year).
plusFORT : a suite of tools for FORTRAN programmers comprising SPAG, GXCHK, : QMERGE, CMAKE and others. Platforms : MS-DOS, Windows, Unix (various), VMS, NT Pricing : Commercial - from 700 or $1000 : Educational 40% discount
Pretty-printer: Many options. Can insert declarations for implicitly typed : symbols. Dead code redundant variable removal. Symbol : name-change option. Can use case to highlight symbol type. : Also many F66-F77-F90 conversions. Restructuring : Re-organises spaghetti code using block IF, DO WHILE etc. : Moves code-blocks to minimise control jumps. Can duplicate : code where this helps. Before after complexity metrics. Static Anal. : Comprehensive global COMMON block argument checks. : Identifies globally unused, used but not set set but not : used. System documentation call-tree. Interactive access : to static analysis database. Dynamic Anal. : Insert probes in source code to detect the use of unassigned : variables, array elements char substrings at run-time. Coverage Anal.: Inserts probes in source code to identify execution : hot-spots, untested code. Accumulates usage over a series : of runs. Annotates source files. CMAKE : A bit like make, but doesn't
need a make-file. Automatically: works out INCLUDE file dependencies. QMERGE : Tool for dealing with system-dependent code.Polyhedron Software Ltd.
93 High St. Tel. +44(0)1865-300579 Standlake Fax. +44(0)1865-300232
WITNEY Compuserve 100013,461 OX8 7RH Internet [email protected] United Kingdom
6. PRETTY, sold by Quibus Enterprises, Inc. Restructures GOTOs, also indents, relabels, moves Formats, etc. $149 for MS-DOS, $500 for Unix workstations. Call (719) 527-1384 for more info.
~From: "John D. McCalpin" [email protected] Not too many people use it, but you might want to add TOOLPACK to the list of FORTRAN "lint" packages. Here is the blurb that I send to people who are interested:
TOOLPACK is a large set of utilities written in FORTRAN to do FORTRAN code analysis and transformation.
TOOLPACK begins by actually parsing the program with a fully FORTRAN- compliant parser and then does all the code transformations on the parse and comment trees.
This means that you cannot confuse TOOLPACK by silly FORTRAN-isms that can easily overwhelm more naive utilities (such as ftnchek). For example, TOOLPACK correctly handles statements such as:
D O U B L E P R E C I S I O N A(100,100)
doubleprecision fred
DO I = 1.2
READ(I,J) = 10.
The usual interface to TOOLPACK is a set of 'csh' scripts that run the
various TOOLPACK utilities to do specific tasks.
The ones you will find most useful are: pol, polx, apt, dapt, decs, getlst, and discard. These are the prettyprinter, precision converter, declaration standardizer, and some necessary utilities. See below for more details.
By aware that TOOLPACK is *very* rigorous about the FORTRAN-77 standard. You may or may not consider this an advantage.
The scripts are described by the 'scripts' script, which delivers the following:
getlst Produce a listing showing statement and token numbers. Report
lexical scanning warnings and errors. (3.1.1)
syn Report errors and
warnings detected by lexical scanning, parsing,
and examining a
set of symbol attributes. (3.1.2)
sem Report errors and warnings
detected by lexical scanning, parsing,
and examining an extended
set of symbol attributes. (3.1.3)
pfort Report errors and warnings
detected by lexical scanning, parsing,
examining an extended set
of symbol attributes, checking for unsafe
references, and checking conformance to a portable subset of
FORTRAN. (3.1.4)
statdoc In a user-supplied report template, place information derived
from static analysis to assist in documenting the program. Examples
of information the user may request are COMMON block usage, symbol
attributes, and a graph of subprogram calls. (3.1.5)
inst Instrument a FORTRAN program so that the instrumented program, whenexecuted, produces information about program execution. (3.2.1)
rundoc Execute a program instrumented by inst and, in a user-supplied report template, place information derived from dynamic analysis to assist in documenting the program. For example, the user may determine the frequency of execution of program segments. (3.2.2)
FORTRAN Transformation Facilities
pol Format a FORTRAN program under control of user-supplied options in a Polish option file. (4.1.1)
polx Construct a Polish option file via a menu-driven editor. (4.1.2)
decs Rebuild the declarative part of a FORTRAN program. (4.2.1)
apt Transform a single-precision version of a FORTRAN program to double precision or vice versa. (4.3.1)
dapt Convert precision and rebuild the declarations, combining the functions of apt and decs. (4.3.2)
cname Change the names in a FORTRAN program that satisfy conditions
derived from information in either the lexical token stream or
the symbol table or both. (4.4.1)
lname Transform a FORTRAN program containing long names to a program with standard names. (4.4.2)
stf Rebuild the flow of control in a FORTRAN program to standardized form. (4.5.1)
ucs Transform nests of DO loops matching certain paradigms so that the transformed code executes more efficiently on vector machines. (4.6.1)
Miscellaneous Facilities
fdiff Compare two FORTRAN programs at the lexical token level. (5.1.1)
dac Compare two data files, neglecting certain formatting differences and numerical differences smaller than a given tolerance. (5.1.2)
vcon Create, edit, and retrieve versions of a file contained in a version file. (5.2.1)
discard Remove unneeded files created by the above scripts. (5.3.1)
scripts Print this summary of the scripts. (5.4.1)
The package is known to compile on Silicon Graphics and Sun machines, though the Makefile is reasonably braindamaged.
You will need about 16 MB for the stripped executables on an SGI machine. Figure on double that for compiling the package.....
Have fun!
John D. McCalpin [email protected] Assistant Professor [email protected] College of Marine Studies, U. Del. [email protected]
NAGWare f77 Tools
The NAGWare f77 Tools are a development of Toolpack/1 that raises it from a public domain distribution service to a fully supported NAG product. Large parts of the software have been completely rewritten and considerable new functionality added, although all the old functionality of the analysis and transformational tools is still there.
First released in 1991, the current version, Release 2 contains:
nag_apt - Arithmetic precision transformation. nag_chname - Token based name changer. nag_decs - Declaration standardiser (can generify intrinsics). nag_fcalls - Call tree generator. nag_fxref - Variable cross-referencer. nag_libdoc - Interface lister. nag_lvi - Local variable initialiser. nag_metrics - Software metrics. nag_pfort - Portability verifier. nag_polish - Pretty printer. nag_polopt - Polish option file editor. nag_struct - Restructurer. nag_profile - Profiler and report generator.The tools are available for most Unix and VMS.
These are just some of the many improvements and enhancements that we
have made.
1. The US Military standard extensions (DO WHILE, ENDDO, IMPLICIT
NONE, INCLUDE etc.) have been added to the familiar Toolpack/1
language definition, but analyser tools still report all extensions to
the ANSI standard.
2. The tools have been substantially rewritten to increase the
execution speed. Notably the lexer and parser have been 100%
rewritten to operate faster and give very much better error messages
and error recovery.
3. The user interfaces for the tools are integrated well with the target operating systems. Access is via Unix scripts (or VMS command language) that carry out complete tasks.
e.g. To invoke the Portability Verifier for a mixture of Fortran and Attribute files, with lower case character warnings suppressed: Unix
nag_pfort -nolcwarn a*.f b*.atr VAX/VMS nag_pfort/nolcwarn a*.for,b*.atr The script calls the semantic analyser for the Fortran files and passes the Attribute files straight to the Portability Verifier.
Or, to Precision Transform and Declaration Standardise in one step: Unix
nag_apt -decs file.f VAX/VMS nag_apt/decs file.for
4. User oriented documentation is based around the scripts. A
relatively slim volume provides all the necessary information to run
the tools. A step by step introduction to each of the tools is
provided, with small examples.
5. The portability verifier has switches that allow groups of less
serious messages to be suppressed. For example, all warnings about use
of non standard characters in strings can be switched off.
6. The portability verifier can dump its internal tables to a "library
file" that can be loaded in a subsequent pfort run. This can be used
to provide a definition of argument passage in a subroutine library to
check a program that calls the subroutine library. Library files are
more compact and more efficient than attribute files for this purpose.
7. Include files are dealt with sensibly by default, the lexer knows
about the MIL-STD INCLUDE statement and merges include files. The
polisher, by default, un-includes the included text. Nag_decs, again
by default, does not declare variables declared in include files.
8. Tools are distributed in executable form only. The installation task is therefore minimal.
We are developing a new option to the Portability Verifier to aid in porting to Fortran 90 by allowing Mil. Std. extensions, names up to 31 characters, etc, without the usual errors/warnings.
NAGWare f90 Tools
These tools make use of the front-end of the NAGWare f90 compiler. Currently, only a small suite of tools is offered, but development is on-going. Fixed format input is acceptable, but all output is free format. Release 2 contents are:
nag_polish90 - Pretty printer. nag_decs90 - Declaration standardiser. nag_prest90 - Precision standardiser. nag_chname90 - Name changer. Also a module builder and polish options editor are provided.
Nag_prest90 standardises the precision of REAL and COMPLEX variables using a paramaterised KIND number, the format of which is controlled by options. The other tools are similar to their Toolpack/1 or NAGWare f77 Tools equivalents.
Availability: Most Unix (now) and VMS (soon).
NAG Ltd. NAG Inc.
Wilkinson House 1400 Opus Place Jordan Hill Road Suite 200 Oxford OX2 8DR Downers Grove UK IL 60515-5702
USA Email: [email protected] Email: [email protected] Tel: +44 1865 311744 Tel: +1 708 971 2337 Fax: +44 1865 311755 Fax: +1 708 971 2706NAGWare Web page: http://www.nag.co.uk/1h/nagware.html
Aside from code reformatting, there is the other meaning of pretty printing ...
~From: James F Hall [email protected] ...
Second, on Q12 in the faq, about available pretty printers for Fortran... Some time ago, I found a pretty printer called "lgrind", which converted a Fortran program into LaTeX/TeX. This text could be included in a larger LaTeX/TeX file, or processed immediately. I chose not to use this because I found it was not the best use of my quota, but others may find it useful.
Lgrind may be found using an archie search: archie lgrind ;;;;
2.2.2) Are there pretty printers for FORTRAN? Flowchart generators?
Yes.
One such is SPAG: Authors are
Polyhedron Software Ltd.
Linden House
93 High St.
Tel. +44(0)1865-300579
Standlake
Fax. +44(0)1865-300232part of their plusFORT product. See above.
WITNEY Compuserve 100013,461 OX8 7RH Internet [email protected] United Kingdom
Another is Fortran development Tools from Quibus 714 527 1384
Also FOR_STRUCT from cobalt-blue. Cobalt Blue, Inc., 555 Sun Valley Drive, Suite K-4, Roswell, GA 30076 Tel: (770) 518-1116, Fax: (770) 640-1182 E-Mail: [email protected]
These more than pretty print, they optionally restructure your code (duplicating code as needed to tidy up strange GOTO lists, turning them into IF-THEN chains, and etc.).
~From: [email protected] (Dave Appel)
[email protected] (Bill Gieske) writes: I have tons of old FORTRAN code, most of it in upper case, the majority of it not indented. Is there a code beautifier, either PD or $$ that I can run the code through to improve the readability, hence the main- tainability? Reply to me direct. I will summarize if appropriate. Bill Gieske ATT Bell Laboratories wg%[email protected]
Call "The Connection at
800-336-1166" and ask for
their software catalog.
In their catalog that I have, Sprint 1992, there is an ad on page
39 from AutoCASE Technology. They have a product called
"AutoFLOW-FORTRAN" that lists for $1,995. It claims to automatically
document your existing source code. AutoCASE's number is
408-446-2273.
On page 93 is an ad from POWERLINE Software Inc. Their number is 800-257-5773, 206-623-9204. They offer a product called SOURCE PRINT+, which they call a code management tool with "multi-style formatting with structured code blocking."
They have a Fortran/Basic version for $169, and a Delux Multi-language version for $249. This program is for DOS (MS-DOS presumably) Windows, and OS/2.
Hope this helps.
Features include the ability to draw an interactive structure chart and display coverage, software complexity and performance information on the structure chart. There are also code tracing features, for instance 3 logic diagrams are produced. Common blocks can be traced through the structure charts, including specific variables within common blocks. Hindsight is excellent for documentation, code inspection, and bringing new software engineers up to speed on new code.Summary:
For more information or a free demo copy, contact:
Rich Fienberg, National Account Manager
Advanced Software
Automation, Inc.
3130A Coronado Dr
Santa Clara, 95054
Phone: 408 492-1668 Fax: 408 492-1669 Free Seminars Fridays 2-4pm
Email: [email protected]
Alternative contact (if Dan cannot be reached:
Other tools:
Refine/FORTRAN ("re-engineering tool")
Reasoning Systems Inc
415 494 6201
pub/fortran/fxref.tar.Z from biome.bio.ns.ca.
create cross reference of a FORTRAN program.
CLEAN77 available from Purdue University.
Mail Greg Flint (afc.klaatu.cc.purdue.edu) for more info.
There is a program called TIDY that is available via
FTP from simtel20 pub/msdos/fortran/tidy621.zip on
Cadre Teamwork
Cadre Technologies Inc. Cadre Teamwork is a large suite of integrated
CASE tools that run on Unix and VAX platforms. Their core products
are structured analysis (with real-time extensions) and design,
information modeling, and an integrated data dictionary. More
recently, they have added many extensions, including a C development
environment, C and Fortran reverse engineering (build a structure
chart from source code), testing tools, and others.
222 Richmond
Street
Providence, RI 02903
Phone (401) 351-5950 Fax (401)
351-7380
~From: [email protected] (Steve Lionel) ~Newsgroups: comp.lang.fortran ~Subject: Re: Code formatter for FORTRAN ~Date: 15 Jun 1994 15:02:38 GMT Organization: Digital Equipment Corporation, Nashua NH ~Reply-To: [email protected] (Steve Lionel)
In article [email protected], [email protected] (Jan Gatowski EN/16) writes: |Does anyone know if there exists a (commercial or freeware) FORTRAN |code indenter/formatter? A friend is faced with revamping a largely |unreadable old code and could use any available tools to render it more |legible.
While I was at UK DECUS I attended a talk which described a product called The FORTRAN Partner which has as its capabilities (according to the documemtation I have):
Screening: automatically checking whole FORTRAN programs for
classes of error not detected by compiler
Troubleshooting: analysing programmes interactively to expose
problems or inconsistencies
Porting: moving code to different FORTRAN environments
Standardising: converting code to a consistent style and creating a
framework for documentation
Optimising: optimising code for speed of execution
The product is available on the following platforms:
Alliant FX80
Avalon Vaccelerator AP/30
Digital VAX
(OpenVMS)
Digital Alpha AXP (OpenVMS)
HP Risc Processors
under Unix
IBM PC and compatible systems with minimum 80386
processor
and Maths Coprocessor
IBM Risc System 6000
under AIX
Parsys Supernode under Idris
Silicon Graphics
MIPS processors under IRIS
Sun SPARC and compatible under Solaris
and SunOS
The vendor is:
A single workstation/PC price is given as 945 Pounds. I don't know what a US price would be.Software Validation Limited PO Box 270 Swindon SN4 0TQ England
Tel: +44 (0) 793 740002 Fax: +44 (0) 793 740974
One of the claims which impressed me was the ability to understand many different syntax variants and convert them to a more standard form. The formatting rules are customizable. (The optimizations consist of inline expansion and loop unrolling.)
I have not actually tried this product (I just got a demo disc today) and this should in no way be considered an endorsement of the product by either myself or Digital Equipment Corporation. However, it looks like it would be worth considering for some applications. --
Steve Lionel Mail: [email protected] SDT Languages Group WWW: http://www.digital.com/info/slionel.html Digital
Equipment Corporation 110 Spit Brook Road, ZKO2-3/N30 Nashua, NH 03062-2698 "Free advice is worth every cent"
[email protected] (Thomas Koenig)
FWEB is available via anonymous ftp; use archie(above) to
determine current location(s).
As for the more general question, what is WEB .... WEB is a "literate" programming system created by Knuth (he of reference book fame, and TeX fame, and etc.). It permits the programmer to write code and documentation together. WEB takes the "high level code and documentation" and creates real publishable documentation (using TeX or LaTeX) and compilable code. WEB versions for many languages are available.
Some features of FWEB are:
1) FWEB is a pretty printer. Code is pretty printed by sending the
FWEB file through "fweave" and "TeX". fweave inserts TeX control
characters around the code for pretty printing. Fweave also collects
a cross-referenced index of *all* identifiers and prints them at the
end of the code listing.
2) FWEB has built in macro preprocessing, which *does* understand FORTRAN syntax and code layout rules. A line extending beyond column 72 will be broken into proper continuation lines.
3) FWEB is multilingual: it understands C,C++,f77,f90, and RatFor.
Thomas Koenig, [email protected], [email protected] If you use EMACS, you can use M-x fortran-mode. An extended version, which includes the fortran-auto-fill-mode minor mode, is available via anonymous ftp from hallc1.cebaf.gov [129.57.32.62] in the directory /emacs.
More generally, Unipress emacs has a Fortran mode. There are XEDIT, BRIEF, TPU and EDT clones available on many common platforms these days.
~From: [email protected] (Bernd R Eggen)
Torbjorn Einarsson has made available Fortran 90 modes for Emacs 19.x (and xemacs). They are available e.g. from the Mailbase list for Fortran 90, comp-fortran-90 from 12/Jan/1995 onwards. I would like to express my gratitude to Torbjorn Einarsson for making this valuable tool publicly accessible.
Files can be retrieved either via anonymous ftp to mailbase.ac.uk, directory /pub/lists/comp-fortran-90/files/, by Gopher and W3 (World Wide Web, URL (Universal Resource Locator) gopher://nisp.ncl.ac.uk/11/lists-a-e/comp-fortran-90/files ) or by sending an e-mail to [email protected], containing the command send listname filename (e.g. send comp-fortran-90 f90.el).
~From: [email protected] ("John E. Davis")
In article
[email protected] [email protected] (chiba)
writes:
2.2.4) Fortran text editors? [...] More generally, Unipress emacs has a Fortran mode. There are XEDIT, BRIEF, TPU and EDT clones available on many common platforms these days.
In addition, JED has a Fortran mode that is very much like the emacs Fortran mode. JED also has a very nice EDT emulation and runs on MSDOS, Unix, VMS, as well as DEC Alpha systems.
The latest version of JED is on amy.tch.harvard.edu in pub/jed. Archie will show it elsewhere but these versions are somewhat dated. The latest version is 0.95. Despite the fact that the version number is below 1.0, the editor is VERY stable--- the version is below 1.0 because I feel that the documentation is not quite up to 1.0 levels.
Here is a partial list of features:
runs under Unix, VMS, and IBMPC (all versions) X Window version also available emacs*, wordstar*, EDT* emulation C, Fortran*, tex*, text editing modes C-like extension language called S-Lang. user configurable (bind keys, write functions, etc....)
region highlighting (even on character based terminals!) Syntax highlighting in Beta test (even on character based terminals) 8 bit clean, edit binary files too. rectangular (box) cut/paste backup and autosave files full undo regular expressions GNU Emacs compatable info reader* calendar* mail*, elm like rmail* (rmail new in 0.95 version) dired directory editor* automatic horizontal pan/scroll (configurable) parenthesis matching/blinking filename, buffername, function name completion Menu driven for novice users*
incremental search/replace* sorting no hardcoded buffer/line limits multiple windows and buffers keyboard macros with macro query feature. buffer mode lines are configurable, e.g., display time, line number, etc... ispell* shell commands and ``interactive'' shell*
* Note: these functions are written in the extension language.
Source code conversion program from ftp
Many people who start to code in Fortran 90 prefer to do so using the new, less restictive, source form. However, a problem arises when wanting to modify old FORTRAN 77 code while sticking to the new style. To help in this situation, a source code conversion program has been written (and well tested) and made availble by anonymous ftp.
Apart from the conversion, the program can:
ensure that blanks are used correctly in the code as they are significant with the new source form;
indent DO-loops and IF-blocks;
replace CONTINUE by END DO, where appropriate;
add subprogram names to END statements;
change non-standard length specification syntax, like INTEGER*2, to the Fortran 90 equivalent, in all contexts (type statements, FUNCTION statements, and IMPLICIT statements);
produce an interface block automatically from the source code of a procedure - useful to the library developer when wishing to use this important new facility with an existing library.
The source code can be obtained by anonymous ftp to jkr.cc.rl.ac.uk (130.246.8.23). When prompted for a userid, reply with anonymous
and give your name as password. The directory is /pub/MandR and the file name is convert.f90.
Mike Metcalf
([email protected])
2.2.6) What is preprocessing, how can it help? How can it hurt?
Preprocessing often refers to usage of a Macro-prepressor upon ones source code prior to compilation.
How can this help?
It can make it easier to move code between machines.
How can this hurt?
It can cause difficulties in compilation of the processed code; most (if not all) macro-preprocessors know nothing about Fortran syntax and code layout rules. So, a common problem is that after preprocessing some text may be lost past "sacred" column 72. Those working with compilers that optionally compile *past* line 72 should probably employ that option when using a preprocessor.
Common prepressors are: cpp, m4, and ratfor. Many sites have their own
custom prepressors. Basic functions are:
1) definition of a symbol
2) conditional code selection based on a symbol
3) substition of a symbol by its definition
Traditional BSD Unix f77 processors treat a file named foo.F (as opposed to foo.f) as one that should be run through cpp prior to compilation "automatically".
2.3) Fortran Packages and libraries
2.3.1) Where can I get "foo" (some random package)
contributed by:
Marc R. Roussel
[email protected]
Use archie. archie is an online database of what is available and where on the "net". Archie can be used either via telnet or by mail. For information about archie send
mail [email protected]
subject: help And you will get back copious directions on how to use archie. If you prefer interactive experimentation, telnet to
archie.rutgers.edu and log in as archie. No password will be required. The first thing you will be shown is a list of other archie servers. If one of these servers is geographically much closer to you than Rutgers, NJ, please disconnect (by typing 'quit') and use that one. To save you this step, here is a list of archie sites:
archie.rutgers.edu 128.6.18.15 (Rutgers University)
archie.unl.edu 129.93.1.14 (University of Nebraska in Lincoln)
archie.sura.net 128.167.254.179 (SURAnet archie server)
archie.ans.net 147.225.1.2 (ANS archie server)
archie.au
139.130.4.6 (Australian server)
archie.funet.fi
128.214.6.100 (European server in Finland)
archie.doc.ic.ac.uk
146.169.11.3 (UK/England server)
archie.cs.huji.ac.il 132.65.6.15
(Israel server)
archie.wide.ad.jp 133.4.3.6 (Japanese
server)
I believe that all of these servers run the mail server as well as the telnet and archie server software. (The archie server is a third way to use archie. It's probably the best way, but it requires that you install software.)
Once you logged into an archie server, you will want to make sure that all the information you will retrieve will be mailed to you. Type
set mailto [email protected]
where, of course, you will substitute your own email address for the made-up one shown above. You are now ready to search the database. If at any time you want to know what options are available to you, type help. To search for a program or file, type
prog foo where foo is the name of the program or file required. Once
your search is done, type 'mail' to have the output sent to you.
(The output will almost always be several pages long.) Then type
'quit' to exit.
2.3.2) Where can I find coded BLAS (and what are coded BLAS?)
The BLAS (basic linear algebra software) comes in several flavors: BLAS-1, -2, and -3. These can be described as scalar, vector and matrix-matrix levels. "Coded" BLAS are either hand coded in assembler, or at least tweaked for a given machine. Some vendors provide these, some are provided on the net (see archie) and some are marketed by various commercial organizations.
In addition, it should be noted that BLAS-3 is very amenable to parallel processing. Done cleverly, this could be done by a network of processors over a net. DSS markets just such an implementation. Contact the folks below. The following material is their marketing blurb
DSSLIB is the fastest BLAS[123], LAPACK, LINPACK, FFTPACK, and VFFTPACK available for the entire SPARC hardware and software line. DSSLIB is based on LAPACK 2.0, but is backward compatible with all previous LAPACKs. Single-CPU optimization typically yields 2x-4x over Netlib code. MP computation yields significantly better than that, reaching almost half a gigaflop on atop-of- the-line Sun MP machine and exceeding even that on SPARC MP supercomputers. Interfaces are shipped with DSSLIB to allow users of IMSL/Math, Rogue Wave's math libraries, IDL from Research Systems, and others to optimize and parallelize their applications without making source code changes.
The company can be contacted at: Dakota Scientific Software, Inc.
2241 Cedar Drive Rapid City, SD 57702-3245
+1.800.641.8851 voice +1.605.394.8851 voice +1.605.348.9623 fax
2.3.3) Where can I get mathematical software
There are, of course, many commerical operations which provide high quality software. NAG and IMSL to name just two.
netlib and archie (mentioned above) can be used to good effect to find specific freeware (public domain, shareware or mostly freely distributable source).
In addition, NASA's COSMIC distributes some government funded software. One particular bit of NASA software, MATH77 a large math library created by numerical analysts at JPL is available from:
Language Systems Corp.
441 Carlisle Dr.
Herndon, VA 22070
(800) 252-6479
email: [email protected]
~From: [email protected] (Michel Olagnon, Ifremer DITI GO, 98.22.41.4
The CADNA package implements stochastic arithmetic (a sort of interval arithmetic) in Fortran 90 on the top of any standard Fortran 77 program. That is, if you have a working Fortran 77 program, you can use CADNA to see what results you get with stochastic arithmetic.
For information on CADNA, or a demo version,
contact
Mr. F. CHAUVET or Mr. BERTHON
AERO
3 Avenue de l'Opera
75001
PARIS
tel: +33 1 44 55 30 80
fax: +33 1 40 15 95 54
For information on stochastic arithmetic (similar to interval arithmetic, but the intervals are the most probable error bounds instead of the maximum bounds), refer to:
Vignes, Jean, A stochastic arithmetic for reliable scientific computation MATCOM 940 - Mathematics and Computers in Simulation 35 (1993) 233-261.
~From: [email protected] (Thomas Koenig) ~Reply-To: [email protected]
You might try the XSC series of languages developed at the Institute for Applied Mathematics at the University of Karlsruhe (look at
http://ma20.rz.uni-karlsruhe.de/~ae08/iam/html/xsc-sprachen.html
if you've got access to Mosaic), or send mail to
[email protected] (Rolf Hammer) for more information.
I'm fairly sure about Pascal, C, and C++; I also believe IBM sells a
compiler based and their VS series of compilers.
2.3.5) FLIB Announcement ... Freeware
Date: Mon, 22 May 1995 19:39:41 Organization: Kansas State University Lines: 93 Message-ID: [email protected] NNTP-Posting-Host: s20.slip.ksu.edu Keywords: FORTRAN Freeware X-Newsreader: Trumpet for Windows [Version 1.0 Rev A]
Hello FORTRAN People,
This is the first general announcement of the FORTRAN Library (FLIB). One of the unique aspects of this code repository is that a considerable amount of source code is available for non-numeric tasks, .e.g., string manipulation, time and date functions, conversion of numbers to strings (and vice versa), etc... Many of these tasks are among the most Frequently Asked Questions (FAQ) in the FORTRAN usenet group.
The preferred (by me) method of accessing FLIB is through the World Wide Web. The information and code descriptions provided via the web will be more up-to-date and comprehensive, and it will be easier for you to maintain a stable link to this code repository if you access it via the uniform resource locator (URL)
http://www.engg.ksu.edu/~robs/flib/flib.html
FLIB can also be reached by generic file transfer protocol (ftp). If you have trouble accessing FLIB via your web client, try using a generic ftp program to access the anonymous ftp server at
Login as anonymous and enter your email address (e.g., [email protected]) as the password. The flib files are under the directory ~pub/robs/flib.
The current scope of the code in FLIB is summarized below. Please feel free to send me an email message describing your opinion/experience with FLIB (remember however that this is freeware).
Rob Stewart [email protected]
The FLIB routines are currently divided into five areas:
CharPak
This package contains approximately 50 routines to manipulate character strings (e.g., upper to lowercase, removal of specific characters from a string, macro substitution). convert numbers to strings and vice versa, align/center text in specific columns, plus more...
GeomPak
For now this package contains less than 10 routines; basic routines are provided to scale, rotate, and translate points between coordinate systems. These routines are quite useful in a number of computer simulations involving 2 and 3-dimensional geometries -- including graphics.
RanPak
This package contains approximately 30 routines to generate random numbers sample from various probability density functions (pdf) including a disk, plate, box, sphere, and unit direction vectors from arbitrarily oriented cones (NOTE: some routines call routines from GeomPak). All of the algorithms for random number genration are based on the discussion of Lehmer generators (circa 1951) in the article
Park, S.K. and Miller, K.W., Random number generators: good ones are hard to find. Communications of the ACM, 31, No 10 (Oct. 1988).
TimPak
A set of routines to access and manipulate the system time and date, compute the elapased time between two events, etc... Since most of these routines are system and compiler dependent, you will also need to select the appropriate file from the Compiler Abstraction Layer (CAL) -- see below.
Compiler Abstraction Layer (CAL)
A set of stubs or wrappers for widely used but non-portable and non-standard system calls or routines (e.g., system time and date).
Rob Stewart [email protected] --or-- http://www.engg.ksu.edu/~robs/home.html
Diplomacy: The art of saying "nice doggie" until you can find a rock.
3.1) Fortran and other languages (Essentially C)
3.1.1) "Why do people use FORTRAN?, C is so much better"
One should avoid such pointless arguments .... if you feel this way, don't subscribe to comp.lang.fortran.
This sort of question always triggers off a protracted discussion, the highlights of which are typically:
a) FORTRAN and C have different semantics. A FORTRAN optimizer knows more about aliasing, function interactions, and I/O. A C optimizer has to infer or compute such information. C bigots typically have neither written such optimizers nor worked with folks who do it for a living, and are prone to dismiss such arguments as being petty and neolithic.
enter Peter van der Linden author of "Expert C Programming"FORTRAN programmers are often a bit more in touch with high performance computing, and are unwilling to bet that heavily on compiler wizardry.
NOT as a +(32760 + b)In addition, ANSI C section 2.1.2.3 on Program Execution makes it clear that associative and commutative regrouping of operands is only allowed if it produces the same result as it would if the regrouping had not been done. Where it makes a difference is on hardware that produces an exception on arithmetic overflow, and the regrouping either causes or avoids an exception, that otherwise would not/would take place. In ANSI C a = a + 32760 + b MUST be evaluated as (a + 32760) + b
UNLESS the overflow exception will be the same in either case.
Fortran is somewhat less tightly-buttoned about this, and
allows the compiler-writer to regroup the expression and evaluate it
in either order. Thus, in Fortran, whether you get an
exception or not depends on the compiler, the level of
optimization, and the hardware. In ANSI C, itonly depends
on the hardware.
Of course, compiler options, vendor extensions and the like
sometimes narrow the difference. Also, some Fortran
compilers do not take advantage of all of these features of
the language, thus narrowing the gap in the other direction.
b) There is a vast body of existing FORTRAN code (much of which is publically available and of high quality). Numerical codes are particularly difficult to "vet", scientific establishments usually do not have large otherwise idle programming staffs, etc. so massive recoding into any new language is typically resisted quite strongly.On any given code, on any given system, all bets are off.
c) Fortran tends to meet some of the needs of scientists
better. Most notably, it has built in support for: - variable
dimension array arguments in subroutines - a
compiler-supported infix exponentiation operator which is
generic with respect to both precision and type, *and*
which is generally handled very efficiently or the
commonly occuring special case
floating-point**small-integer - complex arithmetic -
generic-precision intrinsic functions
d) Retraining staff is quite expensive.
e) It is sometimes argued that: - Jonathan Thornburg also responsible for misc. other fixups
Fortran tends to be easier for non-experts to learn than C, because
its "mental model of the computer" is much simpler. For
example, in Fortran the programmer can generally avoid
learning about pointers and memory addresses, while these are
essential in C. More generally, in Fortran the difference
between (C notation) x, x, and often even *x is basically
hidden, while in C it's
exposed. For non-experts this makes Fortran a considerably
simpler language.
Because of this relative simplicity, for simple programming tasks which fall within its domain, (say writing a simple least-squares fitting routine), Fortran generally requires
much less computer science knowledge of the programmer than C does,
and is thus much easier to use.
3.1.3) How do I call f77 from C (and visa versa) This is quite
platform dependent. For Suns see the FORTRAN User's Guide, Chapter 14.
There is a package available from usenet which attempts to make this "quick and easy" for a wide range of platforms:
Host ftp.germany.eu.net
Location: /newsarchive/comp.sources.misc/volume20 DIRECTORY drwxr-xr-x 512 Jul 7 1993 cfortran
Host ftp.sunet.se
Location: /pub/usenet/comp.sources.misc/volume20 DIRECTORY drwxrwxr-x 512 May 28 1993 cfortran
Host ftp.wustl.edu
Location: /usenet/comp.sources.misc/volume20 DIRECTORY drwxr-xr-x
8192 Oct 30 15:09 cfortran
Host halcyon.com
Location: /dec/.0/usenet/comp.sources.misc/volume20 DIRECTORY dr-xr-xr-x 512 Jul 8 1993 cfortran
Host lth.se
Location: /pub/netnews/sources.misc/volume20 DIRECTORY drwxr-xr-x
512 Jun 7 1993 cfortran
Location: /pub/archives/comp.sources.misc/vol20 DIRECTORY drwxrwxr-x 512 Jun 2 1993 cfortran
It is on many other sites (around the world) too. See archie if you need other pointers.
For some systems, you have to initialize a runtime system explicitly if you call a different language, and stopping execution from the other program may not work.
The most recent version of cfortran.h is available via anon. ftp at
zebra.desy.de.
;;;;
Hello, we have some programs written in C calling the NAG library
(which is written in Fortran). There are a number of important
things you must be aware of:
1) Fortran uses a column wise storage of matrices while C stores them row wise. This means that when you want to parse a matrix from your C-program to the NAG (-fortran-) routine you must transpose the matrix in your program before entering the routine. Of course, any output from such a routine must be transposed again.
If you ommit this step, then probably your program will run (because it has data to compute on) but it will generate wrong answers.
B.T.W. if you have the Fortran source code (of any routine) then on some platforms you may use compiler directives specifying
that the Fortran compiler must use row wise storage. Some platforms
support these directives. However watch out with this if you call the
same routine from another Fortran routine/program.
2) Your Fortran compiler may add an underscore "_" to the routine
name in the symbol table e.g. subroutine example(..,..,..) becomes
example_ in the table. Hence in the calling C-program/routine you
must add a trailing underscore ! Otherwise the loader will complain
about an undefined symbol "example" while "example_" is loaded.
However, check your compiler for this. For example the Fortran
compiler on VAX-VMS systems does NOT add a trailing underscore (there
watch out with the fact that the VAX-Fortran compiler translates
everything in uppercase).
3) Fortran passes its variables by reference. This means that you MUST
give adresses in your calling C-program (i know, this is a stupid
remark but it is too often forgotten (my experience ....)).
4) Watch out especially with float's and double's. Make sure that the size of the variable in the calling program is identical to the
5) Remember that the array index in Fortran starts at 1 while in C
this is at index 0; hence a parsed array fortran_array[1:100] must be used in the C-routine/program as c_array[0:99].
Good luck with it !!
I do a lot of this. The following is true on the following machines. I cannot say about others.
Sun 3 4 IBM
RS/6000
SGI
DECstation
Intergraph Clipper (Apogee Green Hills
compilers)
H-P 7xx
1) If possible, do not pass strings to FORTRAN from C
or vice versa.
2) Do not mix I/O on the same file descriptors.
3) Do all your math in FORTRAN, and all the rest in C if at all possible.
4) NEVER ever attempt to write the equivalent of a FORTRAN function
that returns a character variable in C. Life is too short for the
suffering it causes.
5) If you do ANY I/O in FORTRAN, you MUST use a FORTRAN mainprogram.
6) FORTRAN always passes pointers. not necessarily khb
7) FORTRAN passes string lengths BY VALUE in the order the strings
appear in the argument list. These do NOT appear in the FORTRAN
argument list, but will appear in the C argument list.
8) You will need to take care of nulls and blanks spaces explicitly
if you ignor
9) The Sun FORTRAN compiler used lex and yacc to do the conversion of
a run time format from a character variable. If you use lex and yacc
either rename the variables and functions or partially link before you
link to the FORTRAN libraries.
10) FORTRAN symbols have trailing underscores appended. Some
compilers require a compiler flag to get this. Use it! It makes the
code more portable.
11) Don't pass structures. If you must access a structure element,
pass a pointer through to a routine which passes back the element
pointer.
12) Don't forget that the storage orders for arrays is opposite and transposition is expensive.
I currently have many lines of code with FORTRAN calling C calling FORTRAN. It's not my choice of things to do, but it works well. Much better than using the wrong language for the task. My only regret is that I'm forced to pass a lot of strings between the two languages.
Mobil Exploration and Production TechnologyOffice: (214)-851-8547 [email protected] Home: (214)-306-3907
Reginald H. Beardsley Contract Consultant/Programmer
It is important that you know what's happening when Fortan and C access array elements. But I never had to perform any "transposition" step in a program. You just have to read the definitions the other way. When the manual says A(j+1,i+1) I understand this means a[i][j] in C, etc.
This is true enough, but there are times when you don't want to modify already existing FORTRAN and C you may have to write a transposition wrapper.
This can be advisable for reasons of clarity (i.e. keeping the documentation the code and the math in sync.) and for reasons of performance.
Later, Andrew Mullhaupt
;;;;
Most vendors have surprisingly complete documentation of this sort of thing ... if one troubles to look for it. There is, for example, an entire chapter in the SunPro Fortran documentation khb
3.1.2) Why are there aimless debates?
There are some persistent individuals who would like computer systems to work in a fashion somewhat unlike they do now. It seems pointless to debate with them; the debates (in various groups) always take the same form and never result in meaningful dialog.
One can usually recognize such by reading a week or so's worth of postings. Sometimes you may have to read for a month to recognize such. When you do, please try to avoid triggering (or responding to) such individuals.
Many (if not most) newsreaders support a feature entitled KILL files. As you recognize individuals, you may wish to put them into your local kill file. For example, the style employed by GNUS:
the first kills off all postings from the named individual, the second kills off all postings including the beloved "test" string. See your local NewsGod for details suitable for your local system.(gnus-kill "From" "[email protected]";) (gnus-kill "Subject" "test")
3.1.4) For whatever reasons, I want to translate my Fortran into C. What tools are available?
f90 from NAG, see above f2c see above.
FORTRAN=C=FORTRIX=Rapitech Rapitech (914) 368-3000
FORTRAN=C=FOR_C=Cobalt Blue (770) 518-1116, Fax: (770) 640-1182
E-Mail: [email protected] 518 1116
FORTRAN=C=PROMULA.FORTRAN=Promula (614) 263-5512
Regretably none. This is indeed unfortunate, as even a limited translator could help with typical C header files.
3.2) Compiler and system differences
3.2.1) My compiler is mis-behaving; who enforces the standard?
ANSI and ISO standards do not usually have a particular enforcement mechanism. Local bodies sometimes do.
However, it should be borne in mind that if *your* source code is not standard compliant there is *NO* obligation for a FORTRAN ('77 and before) compiler to do *ANYTHING* in particular. In Fortran (90) the text in "constraints" must be tested and a warning produced (compiler option can be used to evade this, of course).
Some (notably Guy Steele, with respect to another standard) have noted that when non-standard complying code is encountered, a compiler may do *ANYTHING* including initation of Global Warfare. Keep this in mind.
When you do find a bona fide compiler bug, you are generally best served by reporting it to the *vendor*. If you neglect to tell the vendor, how can you complain about it not being fixed?
When reporting a *suspected* bug be sure to be quite specific about the computer system, operating system rev level (patches applied if known) and *compiler*version* (and patches thereof). It is very hard for people to read your mind; but they will try. The attempts are often entertaining, sometimes helpful, but always an inefficient use of people-time and net-bandwidth.
Also note that it is generally helpful if you cut down the example to
the smallest size you can. Vendors are developers too; the
tendency is invest time/money where one can get the biggest bang
for the buck.
[email protected] (Thomas Koenig)
Most likely, the program was written with a line length greater than 72. If your compiler supports it, turn on the option for greater line length (e.g. -e is not uncommon) ; otherwise, split up the lines by hand, or via one of those pretty-printers/restructing tools mentioned above.
Original [email protected] (Thomas Koenig) Revised by [email protected] (Melvin Klassen)
There are different reasons why this could happen. Possibly, your program violates the standard in some way which is not caught by the compiler on system1, or in some way which the compiler on system1 intentionally allowed, e.g., in FORTRAN 77, variable-names were restricted to 6 upper-case characters, while many compilers were extended to handle longer, mixed-case names.
Some programs rely on the retention of values between invocations. Use SAVE statements for those variables which you need to keep across function calls.
Some programs rely on variables to be initialized to zero when a subroutine or function is first called. Some compilers (VAX/VMS for example) exhibit this behaviour.
Some operating systems (IBM's MVS/ESA and VM/ESA for example) have been observed to fill with a "zero" value the first time you reference a previously-unused area of virtual storage.
Compilers on newer architectures often fill variables with garbage on each new function call. This is permitted, according to the standard.
The solution is to explicitly initialize all variables.
Your compiler may have an option to trap uninitialized variables; use that to find the trouble spots. For example, the IBM VS compiler will do a static-flow-analysis, and report such errors,
when you specify the 'OPT(2)' option. Alternatively, if you are desperate, try to compile using a flag which forces static allocation of all variables.
Another problem might be that the accuracy of REAL and DOUBLE PRECISION differs between different platforms; that can cause roundoff error to wipe out your results or your program to go into endless loops.
Yet another (and much more subtle) problem can occur if a lot of formatted I/O is employed. The conversion from internal to external representations can introduce very significant errors; much worse on some platforms than others (doing correctly rounded base conversion is expensive).
There are, of course, lots of other possibilities, these are just a starting point.
3.2.4) How can I read my VAX binary data somewhere else?
Some vendors provide bulit in methods (DEC provides this via special options on the OPEN statement). Others provide library support (on SPARC products, with the SunPro compilers, checkout convert_external)
In addition, Accerl8 provides a commerial tool. Contact:
The following three Q's and A's based on email from:Robert Hickler Tel (303) 863-8088 Accelr8 Technology Email [email protected] for more information.
[email protected] (Thomas Koenig)
;;;;
3.3.1) How common is DO ... END DO
It is very common; and of course is part of Fortran 90. Compilers claimed to *not* support it (much shorter list this way)
1) Salford ftn77/Primos version 2) Prime f77 compiler
3) Microsoft Fortran for CP/M 8080/Z80 machines 4) Fujitsu VPxxx UXP/M
compiler
3.3.2) What are ENCODE and DECODE statements, and how are they translated to standard Fortran? How can I convert numbers to character strings (and vice-versa)?
ENCODE and DECODE are vendor extensions to Fortran (invented in the sixties, long before X3.9-1978 added internal I/O to the language) which are most often used to convert data between numeric and character representations. They may be viewed as formatted writes to (ENCODE) or reads from (DECODE) memory. The standard-conforming alternatives are internal write and internal read statements respectively.
For example, INTEGER MONTH, DAY, YEAR
MONTH = 7
DAY = 4
YEAR = 93
C FORM THE STRING 7/ 4/93 IN VARIABLE "DATE"
ENCODE (8,10,DATE) MONTH,DAY,YEAR
10 FORMAT (I2,'/',I2,'/',I2)
The above can be translated as "write 8 characters, formatted according to format 10, storing the results in variable DATE, and using the contents of variables MONTH, DAY, and YEAR as the data to write."
A DECODE statement would be used to reverse the process (extract the variables MONTH2, DAY2, and YEAR2 from the string DATE). Thus:
INTEGER MONTH2, DAY2, YEAR2
Conversion of ENCODE/DECODE to standard Fortran-77 is not difficult. The critical thing to remember is that the variable to be written to (ENCODE) or read from (DECODE) must be a CHARACTER variable which is long enough to contain the string. The first number within the parentheses (in this case 8) is the minimum length to use in a type declaration. Thus a standard- conforming equivalent of the above example is:
DECODE (8,20,DATE) MONTH2, DAY2, YEAR2 20 FORMAT (I2,1X,I2,1X,I2)
CHARACTER*8 DATE INTEGER MONTH, DAY, YEAR
INTEGER MONTH2, DAY2, YEAR2 MONTH = 7 DAY = 4 YEAR = 93
WRITE (DATE,10) MONTH, DAY, YEAR
10 FORMAT (I2,'/',I2,'/',I2)
READ
(DATE,20) MONTH2, DAY2, YEAR2
20 FORMAT (I2,1X,I2,1X,I2)
Although the above example used integers, any other data type may also be used.
[email protected] (Al Stangenberger)