HDTenEightyP/NetNews huggingface dataset:
From: eng10524@nusunix1.nus.sg (RAMASWAMI VISHWANATH)
Subject: simultaneous equations...solutions
Organization: National University of Singapore
X-Newsreader: TIN [version 1.1 PL6]
Date: Sun, 10 Jan 1993 19:19:52 GMT



Dear nettors , 
	writing a program for  a fortran77 project , i have run into a
bad spot . the prg requires a matrix subroutine to calculate values for
a set of equations . but the equations are not in a square matrix form .
most books i have referred to give solutions to n x n matrices only . 
this prg of mine ,( to calcualte deflections of beams under different
loading conditions) uses finite differentiaiton to get a set of
equations . thus the equations are of the form 
		k = x + y + z

and so on giving me a n x 3 matrix . i am yet to find any concrete
methods to solve such a system of equations . could anybody suggest
something ?

thanks
Newsgroups: comp.lang.fortran
From: klassen@sol.UVic.CA (Melvin Klassen)
Subject: Re: inverse matrix (the APL way)
Organization: University of Victoria, Victoria, B.C. CANADA
Date: Sat, 9 Jan 93 01:42:49 GMT

In article <11658@sun13.scri.fsu.edu> jac@ds8.scri.fsu.edu (Jim Carr) writes:
>You must be thinking that f90 will emulate APL in all of its "glory". 
>In APL, the line 
>                   B (leftarrow) 1/A 
>would give you the inverse of A.  

Well, if that's true, then what does the line:
               B (left-arrow) (quad-overstrike-divide) A
do, and what would the line:
               (quad) (left-arrow) 1 / 1 2 4 8
do, since the RHS of the "/" operator is a non-square matrix?  
Newsgroups: comp.lang.fortran
From: ddewolfe@dragon.acadiau.ca (Dave DeWolfe)
Subject: NT questionnaire
Organization: Acadia University
Date: Thu, 7 Jan 1993 14:41:06 GMT

Hi.  I filled out the questionnaire, but the address to which to mail
it doesn't exist as far as my mailer is concerned.

Pls respond to me via email. Thanks.


-- 

--
Dave DeWolfe                    |  e-mail:
Acadia Center for               |  dave.dewolfe@acadiau.ca 
Newsgroups: comp.lang.fortran
From: jlg@cochiti.lanl.gov (J. Giles)
Subject: Design of C++ et. al. (was: Is FORTRAN a viable language?)
Followup-To: comp.lang.misc
Organization: Los Alamos National Laboratory
Date: Tue, 5 Jan 1993 18:44:13 GMT

In article <29250@oasys.dt.navy.mil>, roth@oasys.dt.navy.mil (Pete Roth) writes:
|> [...]
|> A third possibility: the concepts of the language are new, and so the
|> terms "easy to learn/use/describe" are not yet applicable. When we all
|> understand what virtual methods, templates, overloading, private|protected|
|> public, friend, class, etc. mean, *then* the issues will be well defined.

That could explain the traffic on comp.lang.c++ but not that on 
comp.lang.c.  Further, there are other object oriented languages
which don't seem to present such difficulty or cause so much
confusion.  

To be sure, C++ is better than C, and Objective C is better still 
(though not as popular, so its development is falling behind) - but 
the main problem seems to me to be the commitment to backward 
compatibility to C.  

C++ also shares the C characteristic of haphazardness: more and 
more features are "thrown in" rather than a few well designed 
features with greater power.  Hence the presence of all that new 
jargon when a subset should be sufficient.

Finally, if the new concepts are not easy to learn/use/describe,
perhaps the concepts are not worth the effort.  There are other
ways to provide reuse of code, encapsulation, and the other abstract 
objectives which object oriented concepts supposedly promote which may 
be easier to learn/use/describe.  Functional languages are a possibility 
in this regard.

This discussion only has indirect relevance to Fortran.  Eventually,
Fortran implementations will require extensions to provide some
of these features and the observation of the mistakes mad in other
languages will be of importance.  As far as I can tell, it is too
early yet to state conclusively whether OOP is even a good idea
or not (as compared to alternatives like generic procedures or
functional extensions).  In any case, followups are directed to
comp.lang.misc.

-- 
J. Giles
From: bmich@bimacs.BITNET (Ben Michelson )
Newsgroups: comp.lang.fortran
Subject: Re: A VMS Fortran I/O question
Date: 11 Jan 93 19:16:15 GMT
Organization: Math department, Bar-Ilan University, Ramat-Gan, ISRAEL


Is anyone interested in a two page program
written in awk which does indentation
to fortran sources?
It recognizes
the DO ... ENDDO
as well as the DO 10, ...
and works on Vax-type fortran77

I also have an Ada program which creates
reports on the usage of common blocks.
It shows what commons are defined in which functions,
and how they are defined in the different
places.
These programs are *not* bug free.

Please mail responses to
bmich@bimacs.cs.biu.ac.il

...BeN...
Newsgroups: comp.lang.fortran
From: walt@netcom.com (Walt Brainerd)
Subject: Re: inverse matrix
Summary: No
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Date: Fri, 8 Jan 1993 17:11:21 GMT

In article <1993Jan8.134612.18468@news.unige.ch>, pfennige@scsun.unige.ch (PFENNIGER Daniel) writes:
> 
> Is it true that a Fortran-90 programme inverting matrix A would be:
>       B = 1./A
> ?

No; it is important to keep in mind the model that Fortran 90
does _array processing_, not matrix arithmetic.  1./A produces
an array with the same shape of A in which each element is
the reciprocal of the corresponding element of A.  Similarly,
A * B is element-by-element multiplication, not matrix
multiplication.  In Fortran 90, MATMUL(A, B) is an intrinsic
function, but there is no inversion intrinsic.

However, in Fortran 90 it is possible to define a new data type,
called "MATRIX", say, and define A * B to be matrix multiplication
and perhaps a unary operation .INVERSE.
-- 
Walt Brainerd                walt@netcom.com
Unicomp, Inc.                +1-415-949-4052
235 Mt. Hamilton Ave.        +1-415-949-4058 (fax)
Los Altos, CA 94022 USA      "F90--Fortran for the '90s"
Newsgroups: comp.lang.fortran
From: doetzl@rintintin.Colorado.EDU (Joe Doetzl)
Subject: netCDF vs. ncsa HDF
Organization: University of Colorado, Boulder
Date: 11 Jan 93 16:34:36 GMT

I hope this is an appropriate newsgroup for these questions.  How do these 
two packages perform in storing large (> 100 Meg) rectangular gridded arrays?
Which package produces the smaller files, and which package reads and writes
the data faster?  Both packages will be used primarily on a Cray Y-MP.

--Joe
Newsgroups: comp.lang.fortran
From: pfennige@scsun.unige.ch (PFENNIGER Daniel)
Subject: Re: inverse matrix
Organization: University of Geneva, Switzerland
Date: Fri, 8 Jan 1993 17:14:38 GMT

In article <1993Jan8.134612.18468@news.unige.ch>, pfennige@scsun.unige.ch (PFENNIGER Daniel) writes:
> In article <C0I49C.Jrr@athena.cs.uga.edu>, DEANRE@bscf.uga.edu (ROBIN DEAN) writes:
>  |>       Does anyone know of a "good" fortran program for inverting matrices?
>  |> I was looking for a program to use on either a PC or mainframe.  Any help
>  |> would be very much appeciated.
>  |> 
>  |>                                         Thanks
>  |> 
>  |>                                         Rob
>  |> 
>  |> DEANRE@bscf.uga.edu
> 
> Is it true that a Fortran-90 programme inverting matrix A would be:
>       B = 1./A
> ?
> 	Daniel 

Sorry I wanted to code

        B = A**(-1)
        
        Daniel
From: ig25@fg30.rz.uni-karlsruhe.de (Thomas Koenig)
Newsgroups: comp.lang.fortran
Subject: FORTRAN song
Date: 5 Jan 1993 16:14:29 GMT
Organization: University of Karlsruhe, Germany
Reply-To: ig25@rz.uni-karlsruhe.de
NNTP-Posting-Host: fg30.rz.uni-karlsruhe.de

Here's a song parody I wrote some time ago; the original is Billy Joel's
"Pressure".  Hope you'll like it :-)


           FORTRAN

You have to learn to pace yourself
FORTRAN
You're just like everybody else
FORTRAN
You've only had to write Pascal
So far
But you will come to the day
When the only thing that counts
Are megaflops on a Cray
And you'll have to deal with
FORTRAN

You used to call me paranoid
FORTRAN
But even you can not avoid
FORTRAN
You swore that ENTRY's a sure road to ruin
Now here you are with old code
COMMON blocks are misaligned
Assigned GOTOs disturb your mind
And you cannot handle FORTRAN

All grown up and no place to go
Pascal, Prolog,
What do you know?
All your life is a Lisp machine,
Linked lists, quicksort,
What does it mean?
FORTRAN
FORTRAN

Don't ask me for help
You're all alone
FORTRAN
You'll have to code it
On your own
FORTRAN
I'm sure you'll have some cosmic rationale
But here's your program, incomplete,
Two weeks late, three times too slow
Nothing to do but log on now
And write all your code in
FORTRAN
FORTRAN

All your life is Byte Magazine
I read it too
What does it mean?
FORTRAN

I'm sure you'll have some cosmic rationale
But here you are with old code
COMMON blocks are misaligned
Assigned GOTOs disturb your mind
And you have to code in
FORTRAN
FORTRAN, FORTRAN
One, two, three, four
FORTRAN
-- 
Thomas Koenig, ig25@rz.uni-karlsruhe.de, ig25@dkauni2.bitnet
The joy of engineering is to find a straight line on a double logarithmic
diagram.
Newsgroups: comp.lang.fortran
From: dowd@wisper.com (Kevin Dowd)
Subject: Re: rules for efficient programming in Fortran?
Organization: home.
Date: Tue, 5 Jan 1993 03:02:51 GMT

engel@vms.huji.ac.il writes:
: Hello,
: Do you have rules for efficient programming in FORTRAN
: (or suggestions for reading appropriate books)
: so that there is no excessive or unnecessary CPU? If so,
: could you send them to me?
: Thanks,
: Micky Engel
: (e-address: engel@hujivms.bitnet OR engel@shum.cc.huji.ac.il)

Interesting that you should bring that up...  I'm just putting the 
finishing touches on a book about architectures, benchmarking and 
tuning for publisher O'Reilly and Associates.  The book explains 
how various RISC processors get their speed, and how to tweak 
application code so that it "plays to" the processor and, perhaps 
more importantly, the memory system.  It also explains how optimizing
compilers work, how to profile programs and interpret the results, 
and how to structure benchmarks.  To round things out, there is 
material about distributed and shared memory parallel computers--
what they are and how you program them.  

I think that you will find the book valuable if you are curious about 
computer performance, if you need to understand benchmarks for 
purchase decisions, or if you are looking for more performance from 
a machine you already own.  We've worked hard to make it both 
informative and enjoyable reading.  We hope you will like it.  
I'm sorry that it's not available yet, but it will be out in the 
not too distant future.

-Kevin
--
----------------------------------------------------------------------
     dowd@wisper.com -------------> dowd@atlantic.com
                     (soon to be)
----------------------------------------------------------------------
--
From: walt@netcom.com (Walt Brainerd)
Newsgroups: comp.lang.fortran
Subject: Re: Fortran 77 specifications
Summary: I have it
Date: 8 Jan 93 23:46:59 GMT
Organization: Netcom - Online Communication Services  (408 241-9760 guest)

In article <1993Jan8.160618.29480@newstand.syr.edu>, parashar@npac.syr.edu (Manish Parashar) writes:
> 
> Hi:
> 
> I am looking for the ANSI standard specifications for Fortran 77 -
> (I think it is ANSI X3.9)

Of course, the official paper version is available from ANSI in NY.

I just e-mailed the requester an electronic version.
I will do the same for anyone else.  Compressed and encoded,
it is about 250KB, which I can e-mail out of here in 3 chunks.
-- 
Walt Brainerd                walt@netcom.com
Unicomp, Inc.                +1-415-949-4052
235 Mt. Hamilton Ave.        +1-415-949-4058 (fax)
Los Altos, CA 94022 USA      "F90--Fortran for the '90s"
Newsgroups: comp.lang.fortran
From: hjenter@sparky.er.usgs.gov (Harry Jenter)
Subject: Cross Referencing utilities
Organization: U.S. Geological Survey, Reston VA
Date: Tue, 12 Jan 1993 23:00:28 GMT

I'm posting this on behalf of Michele Goze. Please send
all email followups to her. Thanks.

M. Goze writes:

I'm looking for a UNIX Fortran cross-referencing utility that
improves upon fxref's output.  Most of the Fortran files I work
with have multiple subroutines.  It would be most helpful to 
have cross references listed separately for each subroutine,
and preferably integrated into a numbered listing of the 
Fortran file.  Fxref does not examine INCLUDE files and include
the occurrences of the variables in those files in its cross 
references.  A utility that would do so and also list out the
INCLUDE files themselves within the same listing would be very 
helpful.  The functionality I've described is part of the PRIMOS 
F77 compiler.  

I've begun work on a Bourne script to serve as a postprocessor
to fxref to produce the output I'm looking for.  I thought I'd
check to see if any other cross-referencing tools exist which
provide this output already.

 - Michele Goze
   mygoze@swmgrvares.er.usgs.gov


-- 
Harry L. Jenter                        hjenter@sparky.er.usgs.gov
U.S. Geological Survey                 COM: (703) 648-5916 FTS: 959-5916
Mailstop 430, National Center          "Sometimes you're the bug.
Reston, Virginia 22092                   Sometimes you're the windshield."
Newsgroups: comp.lang.fortran
From: maine@altair.dfrf.nasa.gov (Richard Maine)
Subject: Re: A VMS Fortran I/O question
Organization: NASA Dryden, Edwards, Cal.
	<C0CGGB.1tE@news.cso.uiuc.edu> <1993Jan5.061934.15535@chpc.utexas.edu>
	<MAINE.93Jan5095028@altair.dfrf.nasa.gov>
Date: Tue, 5 Jan 1993 18:00:51 GMT

On Tue, 5 Jan 1993 17:50:34 GMT, maine@altair.dfrf.nasa.gov (me) said:

Maine> ISO/IEC 1551:1991 (aka Fortran 90):

Oops.  Make that ISO/IEC 1539:1991, of course (and with a (E) for English
version if you want to be picky).  There is probably some deep Freudian
reason why I accidentally came up with 1551.   Well, ... MIL STD 1551 is a
common hardware bus; maybe there's a connection. :-)

--
--
Richard Maine
maine@altair.dfrf.nasa.gov
From: agnew@gems.vcu.edu
Newsgroups: comp.lang.fortran
Subject: Re: A VMS Fortran I/O question
Date: 4 Jan 93 08:48:45 -0400
Organization: Medical College of Virginia

In reply to Furio Ercolessi's message, could he not simply use

CONVERT/FDL=BLAH DATAFILE.FOO DATASEND.BAR,

where fdl is an fdl taken of an simple file that will send over the net,
and the vms convert utility simply twists the file into it's new form???

wouldn't that be easier than all that coding you guys are talking about???

Jim Agnew

         /^^^\   \ /   Jim Agnew         | AGNEW@RUBY.VCU.EDU  (Internet)
        /      >  ||   Neurosurgery,     | AGNEW@VCUVAX        (Bitnet)
   /\_/     '   \  /   MCV-VCU           | This disc will self destruct in
 /________________>    Richmond, VA, USA | five seconds.  Good luck, Jim..."




In article <C03pyp.E4v@news.cso.uiuc.edu>, ercolessi@uimrl3.mrl.uiuc.edu (furio ercolessi) writes:
> Does anybody know (well, Steve Lionel certainly knows, but maybe
> he's in holiday ...) what should I do to kill the carriage control character 
> on the standard output in VMS Fortran ?
> 
> That is, I would like to be able to code something like
>       PRINT '(a)','Hello'
> instead of
>       PRINT '(1x,a)','Hello'
> in order to bring the code back and forth between Unix and VMS and 
> retain the same behavior  [please don't tell me i have to pipe the output 
> through 'asa' on the Unix side :-)]
> 
> I am sure there is some magic OPEN that does the trick.  If you do
>       OPEN(6,FILE='SYS$OUTPUT',STATUS='UNKNOWN',CARRIAGERETURN='LIST')
> then this fixes the WRITE(6,)  but not the PRINTs.
> The PRINTs go to a logical unit called FOR$PRINT but how should I
> reference it in the OPEN?  Is there a magic unit number associated
> with it? 
> 
> Thanks!
> 
> PS  OK, *real programmers* always use WRITE(6,)!
> --
> Furio Ercolessi
> Materials Research Laboratory           |   Intl School for Advanced Studies
> Univ. of Illinois at Urbana-Champaign   |   Trieste, Italy
> furio@uiuc.edu                          |   furio@sissa.it
Newsgroups: comp.lang.fortran
From: Dave Dodson <dodson@convex.COM>
Subject: Re: inverse matrix
Originator: dodson@bach.convex.com
Date: Fri, 8 Jan 1993 20:16:45 GMT
Reply-To: dodson@convex.COM (Dave Dodson)
Organization: Engineering, CONVEX Computer Corp., Richardson, Tx., USA
X-Disclaimer: This message was written by a user at CONVEX Computer
              Corp. The opinions expressed are those of the user and
              not necessarily those of CONVEX.

I'd like to point out that it is almost never required or desirable to
compute the inverse of a matrix.  Almost without exception, you can do
any computation in which you would use the inverse in a better way that
does not use the inverse.  By 'better' I mean faster, uses less memory,
more accurate, etc.

----------------------------------------------------------------------

Dave Dodson                                          dodson@convex.COM
Convex Computer Corporation      Richardson, Texas      (214) 497-4234
Newsgroups: comp.lang.fortran
From: jlg@cochiti.lanl.gov (J. Giles)
Subject: Re: Dynamic Memory Allocation in FORTRAN, Question
Organization: Los Alamos National Laboratory
Date: Mon, 4 Jan 1993 19:59:42 GMT


To answer the original question, standard Fortran 90 allows dynamic
allocation through two mechanisms (one of which is the very well thought
out ALLOCATABLE attribute, and the other is a very poorly thought out
pointer facility).  The Fortran 77 standard does not allow dynamic
allocation.  The LWG Fortran specification included a pointer facility
(which was both simpler and better than the Fortran 90 version) which
has been adopted by many vendors as an extension to Fortran 77 - most
notably (from my point of view) both Cray and Sun use the LWG pointer
mechanism.

Note: the LWG Fortran specification was written by the DOE Language
Working Group (LWG) in final form in 1982.  I has many features in
it which are more desirable than the Fortran 90 counterparts.

In article <ljdc3hINNqhc@exodus.Eng.Sun.COM>, corbett@lupa.Eng.Sun.COM (Robert Corbett) writes:
|> [...]
|> A few points to observe are
|> 
|>     (1)  FORTRAN 66, FORTRAN 77, and Fortran 90 are all informal
|> 	 names.  The official names of the languages are either
|> 	 FORTRAN or Fortran.

FORTRAN 77 is the designation recommended by the standard document itself
(ANSI X3.9-1978, Forward):

   It is suggested that the designation FORTRAN 77 be used to distinguish
   this standard from previous FORTRAN standards and any possible future
   revisions.

Similarly, "Fortran 90" is actually the *title* of the ISO version
of the new standard.  Whether these designations are *official*
or merely *officially informal*, they are clearly the appropriate
names to use.  As far as I can tell, the Fortran 90 document uses
these terms throughout.  (It solves the question of whether Fortran 77
is upper- or lower-case by using small caps for all letters after the
initial `F'.)

-- 
J. Giles
Newsgroups: comp.lang.fortran
From: DEANRE@bscf.uga.edu (ROBIN DEAN)
Subject: inverse matrix
Organization: University of Georgia, USA
Date: Thu, 7 Jan 1993 20:43:59 GMT
X-News-Reader: VMS NEWS 1.20

      Does anyone know of a "good" fortran program for inverting matrices?
I was looking for a program to use on either a PC or mainframe.  Any help
would be very much appeciated.

                                        Thanks

                                        Rob

DEANRE@bscf.uga.edu
From: ashafie@acsu.buffalo.edu (Afshin Shafie)
Newsgroups: comp.lang.c
Subject: Help needed on Data Structure
Date: 6 Jan 93 15:25:39 GMT
Distribution: usa
Organization: UB

Hello,

I hope this is the right place to ask this question, if not please let
me know.

I want to write a program (database) in C that will run on SunOS 4.1.2.
There will be about 4 fields for each entry and each field could be a 
search field. There is about 10 MB of data, so speed is very important.
The data will be mostly characters. So far, the few books that I was able 
to get my hands on don't say much about implementation of databases.

If you could point me to a book or give me some hints/suggestions on 
what data structure to use for a problem like this, I would really 
apreciate it. 

Thanks in advance.

Afshin
(ashafie@acsu.buffalo.edu)
From: dave@cs.arizona.edu (Dave Schaumann)
Newsgroups: comp.lang.c
Subject: Re: HELP : C programming Guideline
Date: 12 Jan 93 02:49:32 GMT
Reply-To: dave@cs.arizona.edu (Dave Schaumann)
Organization: University of Arizona

In article <C0pBDG.7Ky@news2.cis.umn.edu>, smahn@vx (Seokmin Ahn) writes:
>I am looking for a C  (not C++) programming guideline.

Hmm... let's see... how about these:

  0. Understand the problem you're trying to solve.  The better
     you understand it, the better you can solve it.

  1. Know the language.  The strengths and the weaknesses.
     Think about how to use the strengths in your application
     while avoiding the weaknesses.

  2. Portability is an issue that should be considered early
     on.  The range of target machines (and OS's) can greatly
     effect fundamental design decisions.

  3. Don't abuse the preprocessor.

  4. Adopt a coding style (indentation, brace placement, naming
     conventions, etc) and stick to it.  It's probably best to
     write out the conventions (if they're not already given to
     you).  It's probably also a good idea to make a list of ways
     you think the style could be improved...

  5. Look at other peoples' code.  It will give you a perspective
     you can't find working on your own, and it will also give you
     a better idea of what's good and what's bad.

  6. Know what constructs cause undefined behavior and avoid them.
     As a corollary, avoid overly-complex constructs.

There's also some pointers to style guides available via ftp in the FAQ
(which should still be available at your site -- just search backward
for a post with "Frequently" in the title, and you should find it)

-- 
You unlock this door with the key of imagination.  Beyond it is another
dimension: a dimension of sound, a dimension of sight, a dimension of mind.
You're moving into a land of both shadow and substance, of things and ideas.
You've just crossed over into... the Twilight Zone.
Newsgroups: local.unix.help,comp.lang.c,comp.os.vms
From: larry@eco.twg.com (Lawrence B. Henry III)
Subject: Re: Using C to read Fortran Files
Reply-To: larry@eco.twg.com
Organization: The Wollongong Group (East Coast Operations)
Date: Thu, 7 Jan 93 17:18:49 GMT


In article <1993Jan7.030702.4174@dbased.nuo.dec.com>, lionel@quark.enet.dec.com (Steve Lionel) writes:
|>
|>In article <C0GHCC.Cwp@ccu.umanitoba.ca>, kaarts@ccu.umanitoba.ca 
|>(Kenneth John Aarts) writes...
|>> 
|>>>I have a fortran program that does essentially
|>> 
|>>>	open(unit=1,"test",status='new')
|>>>	write(1,10) 'cArt'
|>>>10	format(a4)
|>>>	end
|>> 
|>>>and then a C program that reads it:
|>> 
|>>>	int d1,d2,d3,d4,d5;
|>>>	FILE *fp;
|>>>	fp=fopen("test","r");
|>>>	fscanf(fp,"%c%c%c%c%c",&d1,&d2,&d3,&d4,&d5);
|>>>	printf("%d %d %d %d %d\n",d1,d2,d3,d4,d5);
|>> 
|>>>The output of the C program is:
|>> 
|>>>  10  65  114  116   13
|>> 
|>>>  LF  A    r   t    CR
|>> 
|>>>However, a fortran program reading the test program does see cArt.
|>> 
|>
|>It is the VAX C Run-Time Library which is doing this to you; it "interprets"
|>the FORTRAN carriage control, turning the leading "c" into an LF, as that's
|>what would happen if you printed the line on a terminal or printer.  WHY
|>it does this I don't know, nor do I know how to stop it, but I thought
|>that at the least you should know where the problem is located.  
|>
|>All I can suggest is that, if possible, open the file from FORTRAN
|>specifying CARRIAGECONTROL='LIST'.  I'll see what I can dig up about
|>solutions from the VAX C end.

Try changing the way you open the file to something like:

i = open("test", O_RDONLY, "rat=ftn");
fp = fdopen(i, "r");

not sure if this solves your problem.. but checking the VAX C documentation
it seem to imply it will.. The "rat=ftn" tells the open call that the record
attributes of the file contain FORTRAN print control.

-Larry.
Newsgroups: comp.lang.c