HDTenEightyP/NetNews huggingface dataset:
From: simon@giaec.cc.monash.edu.au (simon shields)
Subject: adjustable arrays
Organization: Monash University, Melb., Australia.
Date: Tue, 28 Jul 1992 01:21:19 GMT


Hi 
I'm using a 
HP-UX giaec A.08.07 A 9000/720 2001133857
machine. I have programs that I wrote that make use of adjustable
dimensions. They worked fine on our previous HP800 type machine, but
come up with a declaration error on the 720's. Do I need a special
switch to enable me to use adjustable dimensions with the f77 command
?

Thanks

This is the subroutine that makes use of the adjustable dimension
facility.

      SUBROUTINE graph (coords, curves, fname)
      EXTERNAL fill the array
      INTEGER coords, curves
      LOGICAL fill the array
      CHARACTER fname*(*)
      REAL xdra (coords,curves), ydra (coords, curves),tr(curves)
ERROR  __________^^^^^^^^^^
      IF (fill the array (xdra, ydra,tr, coords, curves, fname)) THEN
          CALL graph the array (xdra, ydra,tr, coords, curves, fname)
          CALL do plt
      ELSE
          PRINT *,"Couldn't fill the array so graph was NOT done !!"
          PRINT *,"Sorry about that !!"
      ENDIF
      RETURN
      END

Newsgroups: comp.lang.fortran
From: na@abb-sc.abb-sc.com (Aru Arunasalam)
Newsgroups: comp.lang.fortran
Subject: Re: Fortran Reference Book For Electromagnetic Modelling
Date: 23 Jul 92 19:33:44 GMT
Organization: ABB Systems Control Company, Inc.


In article <1992Jul22.145606.4355@lut.ac.uk>, elrsc@lut.ac.uk (RSChandran) writes...
> 
>Could anyone suggest a reference book for fortran language, which is to be
>used for Electromagnetic modelling. I have seen several books on
> 
>R.S.Chandran
>

The book FINITE ELEMENTS FOR ELECTRICAL ENGINEERS by Silvestor and Chari has
many examples of Fortran Code used for EM stuff. You can get a paperback
version from Cambridge Press.

There is also a book by  SRH Hoole on the same subject that is directed towards
the Numerical EM community.

N Arunasalam                                  na@abb-sc.com
From: jlb@nic.cerf.net (Bruce Johnson)
Newsgroups: comp.lang.fortran
Subject: Re: 64-bit integers from Sun f77
Date: 22 Jul 92 15:13:10 GMT
Organization: CERFnet

While attempting to upgrade to Sun platforms I was told INTEGER*8 would
be supported in the June release of the compiler.  As I did not complete
the task, I cannot say for certain if this occurred.  SGI also had plans
for July so I imagine Sun either achieved their target or will shortly.
From: D.Stevens@uk.ac.uea (Dave Stevens)
Newsgroups: comp.lang.fortran
Subject: Can anyone recommend a good FORTRAN 90 book
Date: 31 Jul 92 16:25:10 GMT
Organization: School of Maths, University of East Anglia
X-Useragent: Nuntius v1.1

Can anyone recommend a good FORTRAN 90 book?
From: yates@a.chem.upenn.edu (John H. Yates)
Newsgroups: comp.lang.fortran
Subject: Re: Why CALL EXIT? (was Re: Question for C ==> Fortran)
Keywords: why ask why
Date: 30 Jul 92 17:27:16 GMT
Organization: University of Pennsylvania

>On some older systems, exiting with a STOP printed some silly information
>that was useful in a BATCH (eek) context, but was annoying in an
>interactive mode.  Using the non-standard exit made for a visually
>clean exit.

exactly why I started using it years ago.

John
yates@a.chem.upenn.edu
From: dik@cwi.nl (Dik T. Winter)
Newsgroups: comp.lang.fortran
Subject: Re: Why CALL EXIT? (was Re: Question for C ==> Fortran)
Keywords: why ask why
Date: 31 Jul 92 00:07:51 GMT
Organization: CWI, Amsterdam

In article <30JUL199215540929@ltp2.gsfc.nasa.gov> gumley@ltp2.gsfc.nasa.gov (Liam E. Gumley) writes:
 >                         So I left it out completely.  At the end of a main
 > program, I typically just close any files, then put an END statement.
 > It works.  Seems to me the only place you should have a STOP statement is
 > at the end of a main program anyway.  So why not do away with it?
 > 
Well, I know of systems were you get a non-zero exit status if your program
does not terminate with a STOP statement.
-- 
dik t. winter, cwi, kruislaan 413, 1098 sj  amsterdam, nederland
home: bovenover 215, 1025 jn  amsterdam, nederland
dik@cwi.nl
From: jac@ds8.scri.fsu.edu (Jim Carr)
Newsgroups: comp.lang.fortran
Subject: Re: Variable seperator for F77 code.
Date: 21 Jul 92 14:09:36 GMT
Reply-To: jac@ds8.scri.fsu.edu (Jim Carr)
Organization: SCRI, Florida State University

In article <1992Jul20.210437.9800@ctr.columbia.edu> anselmo@cumesb.mech.columbia.edu (Andrew P. Anselmo) writes:
>>In article <20JUL92.14460039@wl.aecl.ca>, zinckt@wl.aecl.ca writes:
>>> Hell0 - 
>>> 
>>> I am looking for code which produces a list of variable names from inputed 
>>> F77 code.  I as using F77 on VAX/VMS. I thought I would ask the net before  
>>> I write one myself.
>
>Same question, different machine... what about for Unix boxes?  What 
>options for f77 will give me the same variable listing?

I hesitate to just reply RTFM, but the original requestor could have just 
typed "HELP FORTRAN" and you can get the answer you desire by typing 
"man f77" if the compiler is called f77 on your machine.  You may need 
to look at "man ld" as well.  

The answer is sytem specific.  For example, -qxref does this function 
for the xlf compiler under AIX.  The MIPS compiler on decstations does 
not provide the option, and the DEC f77 compiler requires both -V and 
-show xref to get this listing.  Always check the flags, especially if 
you do not know if -static or -automatic is the default. 

--
J. A. Carr                                    |  "The New Frontier of which I  
jac@gw.scri.fsu.edu                           |  speak is not a set of promises
Florida State University  B-186               |  -- it is a set of challenges."
Supercomputer Computations Research Institute |   John F. Kennedy (15 July 60)
From: burley@geech.gnu.ai.mit.edu (Craig Burley)
Newsgroups: comp.lang.fortran
Subject: Re: Using ! to denote a comment
Date: 21 Jul 92 21:42:07 GMT
Organization: Free Software Foundation 545 Tech Square Cambridge, MA 02139
In-reply-to: elo9246@summa.tamu.edu's message of 21 Jul 92 19:44:00 GMT

In article <21JUL199214442858@summa.tamu.edu> elo9246@summa.tamu.edu (LaNelle Ohlhausen) writes:

   I have seen ! used in a program line in VAX fortran to denote that
   everything following the ! is a comment, e.g.:

	   x=x+1	! This is a comment

   Is this standard Fortran 77 or is it a VAX extension only?

It is not standard.  It is a VAX extension, among other vendors.  Seems
pretty popular, from what I've been able to tell.

   I have used
   this structure in some code which I'm compiling with Cray Fortran77, and it 
   compiles and seems to run OK, but I want to make sure.  I can't find it in
   my usual references...

Fortunately, if you get stuck porting to a machine that doesn't support it,
it's pretty easy to manually search for ! and convert to standard-style
comments (if you have an editor such as GNU EMACS).
--

James Craig Burley, Software Craftsperson    burley@gnu.ai.mit.edu
Member of the League for Programming Freedom (LPF)
Newsgroups: comp.lang.fortran
From: ohl@ips105.desy.de (Thorsten Ohl)
Subject: Re: why are fortran binaries so large?
Organization: Deutsches Elektronen-Synchrotron, Hamburg, Germany.
Date: Thu, 23 Jul 1992 23:17:46 GMT

>>>>> On Thu, 23 Jul 1992 18:47:58 GMT, dedmunds@selkirk.sfu.ca (Darran Edward Edmundson) said:

Darran> Is space for variables being reserved in the data segment
Darran> (like initialized variables in assembly language)?  (i.e. my
Darran> binary is very large even if my code is quite short and simple
Darran> but I have a large array.)

Depends on the compiler.  Some put uninitialized arrays into the DATA
segment, some are smarter and but them into the BSS segment.  Use
size(1) to find out what's going on.

Darran> If this is the answer, is there a way to prevent it (I don't
Darran> have a f77 manual handy)?

At least on Apollos and HP-UX boxes you can trick the compiler to
allocate the offending array in the BSS segment by putting it into a
COMMON block.  Yes, it's a hack, but it can reduce the size of your
binaries tremendously.
--
////// Thorsten Ohl, DESY (-T-), Notkestr. 85, W-2000 Hamburg 52, F.R.G.
///////// net: ohl@crunch.ikp.physik.th-darmstadt.de, ohl@gnu.ai.mit.edu
//////////////////////// voice: +49-40-8998-3699,  fax: +49-40-8998-3282
Newsgroups: comp.lang.fortran
From: ejh@khonshu.colorado.edu (Edward J. Hartnett)
Subject: Re: Using ! to denote a comment
Organization: Cooperative Institute for Research in the Environmental Sciences
Date: Wed, 22 Jul 1992 15:13:02 GMT

In article <BURLEY.92Jul21174207@geech.gnu.ai.mit.edu> burley@geech.gnu.ai.mit.edu (Craig Burley) writes:
>In article <21JUL199214442858@summa.tamu.edu> elo9246@summa.tamu.edu (LaNelle Ohlhausen) writes:
>
>   I have seen ! used in a program line in VAX fortran to denote that
>   everything following the ! is a comment, e.g.:
>
>	   x=x+1	! This is a comment
>
>   Is this standard Fortran 77 or is it a VAX extension only?
>
>It is not standard.  It is a VAX extension, among other vendors.  Seems
>pretty popular, from what I've been able to tell.
>

It's also used in the Sun FORTRAN compilers, and the Convex Fortran compilers.
			Ed Hartnett


Newsgroups: comp.lang.fortran
From: r-larkin@uiuc.edu (Ron Larkin)
Subject: Re: Why CALL EXIT? (was Re: Question for C ==> Fortran)
Organization: Illinois Natural History Survey
Date: Thu, 30 Jul 1992 14:40:27 GMT

In article <1992Jul29.204115.3917@walter.cray.com> wws@craywr.cray.com (Walter
Spector) writes:
>
>In article <1992Jul29.134901.1@slacvx.slac.stanford.edu>,
fairfield@slacvx.slac.stanford.edu writes:
>|> [a bunch of stuff, then...]
>|>         CALL EXIT
>|>         END
>|>
>|> The "CALL EXIT" at the bottom is optional (more-or-less). A "STOP"
statement
>|> would do just as well.
>
>This is something I have never understood in almost 20 years of Fortran
>programming.  Why do so many people use the non-standard CALL EXIT
>instead of the standardized-for-over-25-years STOP statement?
>Is/was there magic associated with it on some arcane systems?

   One possible reason is that one may then later write one's own SUBROUTINE
EXIT that does some clean-up work or that terminates the program in a certain
way.  In this case, though, I would prefer to see the programmer CALL
CLEAN_UP_AND_EXIT (or some other non-confusable name), that does whatever if
any clean-up is required and then STOPs or CALLs EXIT.
   If environment-specific code (even the rather generic CALL EXIT) is
sequestered within a separate module, it's easier to change later (e.g. to
STOP) or to port to another environment.

>Walt
>-- 
>Walt Spector
>(wws@renaissance.cray.com)
>Sunnyvale, California
>_._ _._ _.... _. ._.

Ron

Ronald P. Larkin, Illinois Natural History Survey
607 E. Peabody Drive, Champaign, IL 61820  USA
r-larkin@uiuc.edu (Ron Larkin)
Newsgroups: comp.lang.fortran
From: simon@giaec.cc.monash.edu.au (simon shields)
Subject: dynamic arrays solution from HP
Summary: hps solution
Keywords: dynamic arrays
Organization: Monash University, Melb., Australia.
Date: Wed, 29 Jul 1992 00:36:18 GMT


SYSTEM: HP-UX giaec A.08.07 A 9000/720 2001133857
Hi
Alan from HP wrote to me from comp.sys.hp the following.


From: acmeyer@hpfcso.FC.HP.COM (Alan C. Meyer)
Date: Tue, 28 Jul 1992 14:13:32 GMT
Subject: Re: adjustable arrays 720's f77
Organization: Hewlett-Packard, Fort Collins, CO, USA
Newsgroups: comp.sys.hp

In comp.sys.hp, simon@giaec.cc.monash.edu.au (simon shields) writes:

> I am having problems compiling fortran 77 programs I wrote on an 800
> series that made use of adjustable arrays. I won't compile on the
> 720's we have. 
> 
> The machine I'm using is
> HP-UX giaec A.08.07 A 9000/720 2001133857

	...

>       SUBROUTINE graph (coords, curves, fname)
>       EXTERNAL fill the array
>       INTEGER coords, curves
>       LOGICAL fill the array
>       CHARACTER fname*(*)
> -->>> REAL xdra (coords,curves), ydra (coords, curves),tr(curves)

The arrays xdra, ydra and tr are *automatic* arrays, not adjustable arrays
(automatics are local arrays of non-constant size, and adjustables are
dummy arguments of non-constant size).

S800 Fortran supports automatic arrays, also calling them dynamic arrays.
At 8.07, the S700 compiler does not support this feature.  However, they
have been implemented and will ship with the next S700 release.

Until then, one workaround, which will involve changing the source, would
be to use the Cray pointer feature to dynamically allocate the arrays.  So,
change:

       SUBROUTINE graph (coords, curves, fname)
       INTEGER coords, curves
       REAL xdra (coords,curves), ydra (coords, curves),tr(curves)

to
       SUBROUTINE graph (coords, curves, fname)
       INTEGER coords, curves
       POINTER (ipxdra, xdra(coords,curves))
       POINTER (ipydra, ydra(coords,curves))
       POINTER (iptr, tr(curves))

       ipxdra = MALLOC(coords*curves*4)
       ipydra = MALLOC(coords*curves*4)
       iptr = MALLOC(curves*4)

       ! reference xdra, ydra and tr as usual

       ...
       FREE(ipxdra)
       FREE(ipydra)
       FREE(tr)
       END

Alan Meyer
Hewlett-Packard
Colorado Language Lab
acmeyer@fc.hp.com

"These are my own opinions ..."

Hope this helps someone.
Bye from simon.
Newsgroups: comp.lang.fortran
From: gumley@ltp2.gsfc.nasa.gov (Liam E. Gumley)
Subject: Re: Why CALL EXIT? (was Re: Question for C ==> Fortran)
News-Software: VAX/VMS VNEWS 1.4-b1  
Keywords: why ask why
Organization: NASA-GSFC LTP Computing Facility Code 920.2
Date: Thu, 30 Jul 1992 20:54:00 GMT

In article <131935@lll-winken.LLNL.GOV>, miller@icf.llnl.gov (Pat Miller) writes...
> 
>In article <1992Jul29.204115.3917@walter.cray.com>, wws@craywr.cray.com
>(Walter Spector) writes:
>|> This is something I have never understood in almost 20 years of Fortran
>|> programming.  Why do so many people use the non-standard CALL EXIT
>|> instead of the standardized-for-over-25-years STOP statement?
>|> Is/was there magic associated with it on some arcane systems?
> 
>On some older systems, exiting with a STOP printed some silly information
>that was useful in a BATCH (eek) context, but was annoying in an
>interactive mode.  Using the non-standard exit made for a visually
>clean exit.
> 

Well folks I used to use the STOP statement all the time, but I got
really tired of the message it would print on execution (does it in MS-Fortran
and SGI MIPS Fortran).  So I left it out completely.  At the end of a main
program, I typically just close any files, then put an END statement.
It works.  Seems to me the only place you should have a STOP statement is
at the end of a main program anyway.  So why not do away with it?

Cheers,
Liam.
--
Liam E. Gumley                            | Phone    : (301) 982-3700
NASA/GSFC MODIS Science Data Support Team | Fax      : (301) 982-3749
Research and Data Systems Corporation     | Internet : gumley@ltp.gsfc.nasa.gov
Greenbelt MD, USA                         | Opinions expressed here are my own!
Newsgroups: comp.lang.fortran
From: shinn@agsm.ucla.edu (Shinn-Tzong Wu)
Subject: Fortran unformat format???
Organization: UCLA, Department of Psychology, Drug Abuse Research Center
Date: 28 Jul 92 22:14:17 PDT

I tried to write a C program to read a Lahey (F77L3) generated unformatted
file, but I could not find any document (either in Lahey or Microsoft)
about how to decode the header (FD 13 00 00 00 etc), worse, Lahey's
format is different from Microsoft's!  Would anyone please shed some
light in how to find the doc?  Thanks.


Shinn
Newsgroups: comp.lang.fortran

I can't answer your original question, but am curious as to why 64-bit
integers are important for Fortran users, so I would like to pose a counter
question.

Why do you need 64-bit integers?
I.e. What do you use integers for that requires > 32 bits?

Some possibilities come to mind:

 o For importability from systems whose default integer size is 64-bits.
 o For time or money representation.
 o For representation of quantities (such as distance or length) which more
   naturally would be REAL, but integer operations are faster.
 o For more bit fields in an integer for use as flags.

Or ???


Joan Kauth
Hewlett-Packard  Fortran compiler lab
Fort Collins, Colorado
From: nagrwb@vax.oxford.ac.uk
Newsgroups: comp.lang.fortran
Subject: Re: What are the NAG libraries?
Date: 22 Jul 92 11:36:55 GMT
Organization: Oxford University VAXcluster

In article <10895@platypus.uofs.uofs.edu>, bill@prijat.cs.uofs.edu (Bill Gunshannon) writes:
> OK, for anyone who's interested, here is the address I have for NAG.
> 
> ...stuff deleted...
> 
> That's it.  I can't say if the company is still around, but I would
> guess it is.
> 
See previous posting for correct addresses. And Bill, NAG is very much
"alive and kicking!" to quote Simple Minds.

apologies if this msg gets repeated - usenet feed a little falkey

Richard.
-- 
** R.W. Brankin -- Numerical Algorithms Group Ltd. -- nagrwb@vax.ox.ac.uk **
**   suggestions for sig. welcome   --   will need   include<std.discl>   **
Newsgroups: comp.lang.fortran
From: lionel@quark.enet.dec.com (Steve Lionel)
Subject: Re: adjustable arrays
Reply-To: lionel@quark.enet.dec.com (Steve Lionel)
Organization: Digital Equipment Corporation, Nashua NH
Date: Tue, 28 Jul 92 17:59:47 GMT


In article <simon.712286479@giaeb>, simon@giaec.cc.monash.edu.au 
(simon shields) writes:
|>I'm using a 
|>HP-UX giaec A.08.07 A 9000/720 2001133857
|>machine. I have programs that I wrote that make use of adjustable
|>dimensions. They worked fine on our previous HP800 type machine, but
|>come up with a declaration error on the 720's. Do I need a special
|>switch to enable me to use adjustable dimensions with the f77 command
|>?
|>
|>Thanks
|>
|>This is the subroutine that makes use of the adjustable dimension
|>facility.
|>
|>      SUBROUTINE graph (coords, curves, fname)
|>      EXTERNAL fill the array
|>      INTEGER coords, curves
|>      LOGICAL fill the array
|>      CHARACTER fname*(*)
|>      REAL xdra (coords,curves), ydra (coords, curves),tr(curves)
|>ERROR  __________^^^^^^^^^^
|>      IF (fill the array (xdra, ydra,tr, coords, curves, fname)) THEN
|>          CALL graph the array (xdra, ydra,tr, coords, curves, fname)
|>          CALL do plt
|>      ELSE
|>          PRINT *,"Couldn't fill the array so graph was NOT done !!"
|>          PRINT *,"Sorry about that !!"
|>      ENDIF
|>      RETURN
|>      END

The Fortran language requires arrays with adjustable bounds to be formal
arguments themselves.  That is, XDRA must be a formal argument to the
subroutine.  (In addition, the bounds expressions must not contain elements
other than constants or variables which are themselves formals or in
COMMON.)

What you have tried to do (and also in your subsequent posting) is dynamic
allocation, which is not supported in most Fortran implementations.  If your
implementation has support for pointers (also non-standard), you can couple
these with a call to the operating system's memory allocation services
(eg. C's malloc) to get what you want.
--

Steve Lionel                    lionel@quark.enet.dec.com
Languages Group
Digital Equipment Corporation
110 Spit Brook Road
Nashua, NH 03062
Newsgroups: comp.lang.fortran
From: jal41820@uxa.cso.uiuc.edu (Smiley)
Subject: Re: Segmentation Violation help...
Organization: University of Illinois at Urbana
Date: Thu, 23 Jul 1992 15:28:08 GMT
Keywords: help

jal41820@uxa.cso.uiuc.edu (Smiley) writes:
:)      open(unit=13,file=cendata,status='old',form='formatted')
:) 1013 format (i4,i4,f8.1,f8.1,f9.4,f8.4)
:)   73 read(13,1013,end=93) i,j,dum1,dum2,grid(i,j,1),grid(i,j,2)
:)      grid(i,j,2) = 0 - grid(i,j,2)
:)      go to 73

As an added note, reading in normal variables such as "dum3,dum4" in place
of the array variables on the read line, and then assiging the array values
yields the same results.

Lots of people have been making this suggestion, so I thought I'd mention
it.   :)

(btw, thanks again to everyone who's tried to help...  :)

-- 
        Josh Laff              #     #      
email to: smiley@uiuc.edu     _       _     Hello! I am a signature virus!  
      (217) 356-6079         |#\_____/#|    Join the fun and copy mo*#(*&^!>.
                              \#######/
From: jlg@cochiti.lanl.gov (Jim Giles)
Newsgroups: comp.lang.fortran
Subject: Re: Variable repeat count specifier for FORMAT statments
Date: 24 Jul 92 15:21:29 GMT
Distribution: na
Organization: Los Alamos National Laboratory

In article <1992Jul24.012058.21162@ncsa.uiuc.edu>, hirchert@ncsa.uiuc.edu (Kurt Hirchert) writes:

|> [...]                                            In more complex
|> situations, I would build the format on the fly:
|> 
|> 		      character*80 fmt
|> 		      ...
|> 		      write (fmt,'(a,i3,a)') '(',n,'(I8))'
|> 		      write (*,fmt) whatever_it_is_you_wanted_to_write

Wouldn't it be more legible to write:

      character*80 fmt
      ...
      fmt='(nnn(I8))'
      write (fmt(2:4),'(I3)') n
      write (*,fmt) whatever_it_is_you_wanted_to_write

There is no need to construct the entire value of `fmt' with the internal
write, you need only concern yourself with that part which changes.

-- 
J. Giles
From: fortran@giac1.oscs.montana.edu (Lou Glassy)
Newsgroups: comp.lang.fortran
Subject: Re: Can anyone recommend a good FORTRAN 90 book
Keywords: n
Date: 31 Jul 92 19:23:56 GMT
Organization: Montana State University, Bozeman Montana USA

"Fortran 90 Explained", by M. Metcalf and J. Reid, gives clear
and concise examples of each of F90's new features and changes
wrt earlier Fortrans... Good Stuff.

There is another book (haven't read it yet, but an instructor here has
bought it, thinks highly of it) by W. Brainherd, J. Adams et al, called
(i think?) "Fortran 90: ANSI Standard Reference".

Lou.
-- 
Lou Glassy (fortran@giac1.oscs.montana.edu)          consider alternatives
Newsgroups: comp.lang.fortran
Subject: recursive I/O
From: ecmtwhk@ccu1.aukuni.ac.nz (Thomas Koenig)
Date: Tue, 21 Jul 1992 22:31:57 GMT
Organization: University of Auckland, New Zealand.

Is the following legal F77?  It works on the UNIX box I'm on at the
moment, but I can imagine trouble with architectures which do not use
a stack for argument passing, for example /370. 

C This assumes channels 6 and 0 are preconnected
      PROGRAM MAIN
      WRITE (6,*) FCN(2.3)
      END
      FUNCTION FCN(A)
      IF (A.GT.2.) WRITE (0,*) 'Something horrible happened'
      FCN = 2. - A
      END
-- 
Thomas Koenig, ecmtwhk@ccu1.aukuni.ac.nz, ib09@rz.uni-karlsruhe.de
The joy of engineering is to find a straight line on a double logarithmic
diagram.
Newsgroups: comp.lang.fortran
From: peter@itnux2.cineca.it (Peter Yovchev)
Subject: DOS-UNIX Fortran compatibility?
Keywords: fortran,dos,unix
Organization: Laboratorio di Fisica Computazionale, INFM. Trento Italia
Date: Mon, 27 Jul 1992 12:47:38 GMT

I'm trying to implement a fortran program written for PC on
UNIX computers. 
I succeded to compile it but some of the output results are
completely wrong.
I'm sure that the input data are correct.
I'm also sure that the problem is not in the computer because
I compiled the program with f77 compiler for Sun   and f77 compiler
for Ultrix and the output results were the same. /and wrong/

Can somebody help me?

Please email me.
Thank you.


Peter Yovchev                                  email:peter@itnsun4.cineca.it
University of Trento                                 peter@itnux2.cineca.it
Italy
From: matap@lure.latrobe.edu.au (Andrej Panjkov, La Trobe Maths)
Newsgroups: comp.lang.fortran
Subject: Portability of DIRECT UNFORMATTED data files?
Date: 29 Jul 92 01:15:24 GMT
Organization: VAX Cluster, Computer Centre, La Trobe University

Hi all--

What does the standard say about the internal format of DIRECT UNFORMATTED
data files? 

Will these be portable between systems?  (ie is a D/U file written by
a Fortran program on one system readable by a Fortran program on another?)





-- 

Andrej Panjkov,                       matap@lure.latrobe.edu.au 
Dept. of Mathematics,
La Trobe University,                  "I've got a goddamned PLAN!"
Melbourne, Victoria, 3083, Australia
Newsgroups: comp.lang.fortran