HDTenEightyP/NetNews huggingface dataset:
From: arritt@kuhub.cc.ukans.edu
Newsgroups: comp.lang.fortran
Subject: bad code crashes system
Date: 13 Apr 92 14:02:43 CDT
Organization: University of Kansas Academic Computing Services

I've been using Microsoft 5.0 fortran on my PC for some recent code
development, since the error messages are more informative than on
my "real" computer :-) .... The only major problem I've had is that
compiling bad code sometimes crashes the system.  It locks up the keyboard,
sends stuff to the printer (!), writes gibberish to the screen, and
so on.  Sometimes this can be gotten out of by closing the DesqView
window that I'm running in but other times the system is so locked up
that only a complete power-down will work (i.e., not even a ctrl-alt-del
works).

I've eliminated DesqView as the culprit by trying the same compiles
under straight DOS, which gives similar weird behavior.  It seems to happen
during the compile phase and not during optimization or linking, as
I've had this occur when compiling with the -c and -Od options.
Also I tried a different PC and got the same thing, so it's not likely


ANY advice as to how to avoid this would be appreciated!!!
If there is a particular type of coding error that I can be
careful to avoid, please let me know.
________________________________________________________________________
Raymond W. Arritt                     |  Dept. of Physics and Astronomy  
Assistant Professor                   |  University of Kansas 
arritt@kuhub.cc.ukans.edu             |  Lawrence, KS  66045  
Apr  1 12:29:21 timed[92]: THIS MACHINE IS A SLAVE
Apr  1 12:29:27 timed[92]: THIS MACHINE IS A CANDIDATE
Apr  1 12:29:31 timed[92]: This machine is master
From: peterson@grue.enet.dec.com (Bob Peterson)
Newsgroups: comp.lang.fortran
Subject: Re: my problem is solved
Keywords: FORTRAN77 READ WRITE FORMAT
Date: 15 Apr 92 16:58:30 GMT
Reply-To: peterson@tle.enet.dec.com
Organization: Digital Equipment Corporation


In article <28594@slice.ooc.uva.nl>, noam@ooc.uva.nl (Noam Kloos) writes:
>I received a lot of possible solutions to my problem.
>Many people got upset by my typing error being
>READ(1,99) WRITE(1,99) which should be READ(1,99) WRITE(6,99)
>Anyhow what all said is true, I had to use TWO DIFFERENT FORMAT statements.
>Some suggested for the WRITE FORMAT(1X,A80) others (' ',A80)
>or (1H ,A80), but that all resulted in double spacing my output.
>What bugs me again is that inspired to this feedback I tried
>(1H+,A80) what should mean overwriting text, but no this is actually the
>solution to the problem with my MS FORTRAN77 ver 4.1

I can't say if this applies from a quick reading of your posting... The 
Fortran-77 standard requires that Fortran processors MODIFY hollerith formats
(nHxxx and 'xxx') in FORMATs when you READ using such a FORMAT.  Then if
you turn around and WRITE using that same FORMAT now the hollerith will be 
whatever was read for those columns.  Arcane, huh?

\bob
From: walt@netcom.com (Walt Brainerd)
Newsgroups: comp.lang.fortran
Subject: Fortran Journal contents
Keywords: Fortran
Date: 16 Apr 92 00:02:48 GMT
Article-I.D.: netcom.rgzj2sm.walt
Organization: Netcom - Online Communication Services  (408 241-9760 guest)

FYI: Contents of the Mar/Apr _Fortran Journal_ include:

  o  Object-Oriented Programming in Fortran
     -- Peter Roth of the David Taylor Research Center

  o  A Proposal for Generic BLAS, LINPACK, and LAPACK
     -- Ron Shepard of the Argonne National Laboratory

  o  High Performance Fortran Meeting
     -- Rex Page of Amoco

  o  What is HPFF?
     -- Chuck Koelbel, Rice University

Coming in the next issue:

  o  Tiny Ninety--A Proposal for a Subset of Fortran 90
     to be Used for Teaching
     -- Lou Glassy, Montana State University

If you would like information about the _Fortran Journal_,
please send me e-mail.
-- 
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"
From: mcdowell@cfa.harvard.edu (Jonathan McDowell)
Newsgroups: comp.lang.fortran
Subject: Re: Q format specification
Date: 7 Apr 92 14:01:17 GMT
Organization: Smithsonian Astrophysical Observatory, Cambridge, MA,  USA

From article <11939@tamsun.tamu.edu>, by potter@scan2.tamu.edu (SHANE POTTER):
> While I am here, does anybody know if the Q specification is unique to VAX
> fortran or is this some new standard being developed?
> 
> 						Thanks, Shane

It's a VAX extension, it is not in the F77 standard and as
far as I can see it's not in the new F90 standard.
 
 - Jonathan McDowell
From: mac@cis.ksu.edu (Myron A. Calhoun)
Newsgroups: comp.lang.fortran
Subject: Re: my problem is solved
Date: 14 Apr 92 12:46:18 GMT
Organization: Kansas State University
NNTP-Posting-Host: depot.cis.ksu.edu
Keywords: FORTRAN77 READ WRITE FORMAT

noam@ooc.uva.nl (Noam Kloos) writes:
>I received a lot of possible solutions to my problem.
>Many people got upset by my typing error being
>READ(1,99) WRITE(1,99) which should be READ(1,99) WRITE(6,99)

I/O device assignments are very system DEpendent;
I use "1" for both input and output quite often.


>Anyhow what all said is true, I had to use TWO DIFFERENT FORMAT statements.
>Some suggested for the WRITE FORMAT(1X,A80) others (' ',A80)
>or (1H ,A80), but that all resulted in double spacing my output.

All are also semmantically identical.

>What bugs me again is that inspired to this feedback I tried
>(1H+,A80) what should mean overwriting text, but no this is actually the

I suspect your printer is not set-up correctly!

>solution to the problem with my MS FORTRAN77 ver 4.1
                                 ^^^^^^^^^^^^^^^^^^^^
There's the REAL problem; you are using MicroSoft f77!!!!    :-)
--Myron.
-- 
# We preserve our freedoms using four boxes:  soap, ballot, jury, and cartridge.
# Myron A. Calhoun, PhD EE; Associate Professor  (913) 539-4448 home
# INTERNET:  mac@cis.ksu.edu (129.130.10.5)      532-6350 work, 532-7353 fax
#      UUCP:  ...rutgers!depot!mac               W0PBV @ K0VAY.KS.USA.NA
From: schieb@isis.gsfc.nasa.gov (Brian D. Schieber)
Newsgroups: comp.lang.fortran
Subject: Dear 8mm guru
Date: 14 Apr 92 18:32:20 GMT
Organization: NASA Code 971, Oceans & Ice Branch

wrong newsgroup probably but...

I have a slew of 8mm backup tapes that have been set aside
because of repeated errors in backups. The whole backup 
mechanism on our VAXes is flaky and I'd like to confirm or
deny the integrity of the tapes. 

Does anyone know of a method/utility that could check out
these tapes?

Thanks ahead of time,
 Brian


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  Brian D. Schieber            NASA/Goddard Space Flight Center 
  schieb@shark.gsfc.nasa.gov   Laboratory for Hydrospheric      
  DECnet: urchin::schieb       Processes                       
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
From: macphed@dvinci.USask.Ca (Ian MacPhedran)
Newsgroups: comp.lang.fortran
Subject: F90 Query
Keywords: FORTRAN Fortran 90 F90 f90 compiler
Date: 14 Apr 92 17:53:51 GMT
Organization: University of Saskatchewan

Hi;
I have seen several requests for information regarding Fortran 90
compilers, but no summaries of information received, nor any FAQs.
(Does an FAQ or an archive exist for this group?) As I am also 
interested in this, I will ask this question again.

What f90 compilers are currently available for any architecture or
operating system?

I saw mention of something called NAGWARE f90, which appeared to be
an f2c equivalent (f90 -> c) from the rather brief description. What
is this, and how could it be obtained?

I will summarize answers received.
Thank you in advance.

Ian.
-- 
----------------------------------------------------------------------------
Ian MacPhedran, Engineering Computer Centre, University of Saskatchewan.
2B13 Engineering Building, U. of S. Campus, Saskatoon, Sask., CANADA S7N 0W0
macphed@dvinci.USask.CA  macphedran@sask.USask.CA
Newsgroups: comp.lang.fortran
From: browning@willard.nas.nasa.gov (David S. Browning)
Subject: Re: Format of unformatted files: does a standard exist?
	<1992Apr9.201412.16191@ux1.cso.uiuc.edu>
	<1992Apr10.151307.28643@e2big.mko.dec.com>
Organization: NAS Program, NASA Ames Research Center, Moffett Field, CA
Date: 10 Apr 92 11:10:16

In article <1992Apr10.151307.28643@e2big.mko.dec.com> lionel@quark.enet.dec.com (Steve Lionel) writes:

<> [ ... background deleted ... ]
<>
<> "Type A" is comprised of systems which use IEEE "big-endian"
<> floating point.  Big-endian means that the most significant bit is
<> stored in the lowest addressed byte.  "Type B" is IEEE
<> "little-endian", where the most significant bit is in the highest
<> addressed byte.  Machines based on Intel x86 processors (eg. IBM PC
<> and clones) also use this format, so you can see that the "Type B"
<> group is actually quite a bit larger in terms of total number of
<> systems than "Type A".
<>
<> There are three other popular floating point formats: VAX, Cray and
<> IBM System/370 (all of these predate the IEEE standard.)

With respect to unformatted I/O, there's more to it than just floating
point format.  From the ANSI X3.9-1978 FORTRAN 77 standard, page 12-2,
section 12.1.2, "Unformatted Record":

	An unformatted record consists of a sequence of values in a
	processor-dependent form and may contain both character and
	noncharacter data or may contain no data.  The length of an
	unformatted record is measured in processor-depndent units and
	depends on the output list (12.8.2) used when it is written,
	as well as on the processor and the external medium.  The
	length may be zero.

	Unformatted records may be read or written only by unformatted
	input/output statements (12.8.1).

This means that the standard allows all aspects of the unformatted
record to be processor-dependent, not just the format of the numbers.
You'll typically find other things, such as record start, stop,
length (in processor-dependent units!), etc.  If you want to convert
between vendors' unformatted output, you'll need to more than just the
binary floating point representation of the machine.

-- David

|============================================================================|
| Internet:  browning@willard.nas.nasa.gov          Phone:  (415) 604-4321   |
| UUCP:      uunet!ames!amelia!browning                                      |
|----------------------------------------------------------------------------|
|"the nice thing about true hopelessness is that you don't have to try again"|
| -- jules shear                                                             |
|============================================================================|
From: khafagi@egr.msu.edu (Bassem K. Khafagi)
Newsgroups: comp.lang.fortran
Subject: Need ploting subroutines....
Date: 15 Apr 92 20:06:52 GMT
Reply-To: khafagi@egr.msu.edu (Bassem K. Khafagi)
Organization: Michigan State University
Originator: khafagi@frith.egr.msu.edu

I am writing a software where I need to generate and plot graphs to the monitor.I have been looking for any plotting packages (hopefully shareware) to do this..... I am using MS Fortran 5.x .... Any Help!!!!??? THNKS
From: svanhout@cmsa.gmr.com (Sid VanHouten CT90)
Newsgroups: comp.lang.fortran
Subject: Re: VAX VMS Fortran -> UNIX Fortran?
Keywords: VMS Fortran
Date: 8 Apr 92 12:10:27 GMT
Reply-To: svanhout@cmsa.gmr.com (Sid VanHouten CT90)
Distribution: usa
Organization: General Motors Research Labs

|>From: tcumming@netcom.com (Tom Cumming)
|>Subject: VAX VMS Fortran -> UNIX Fortran?

|>
|>
|>    I have literally megabytes of VMS fortran source that I would like
|>to compile on my UNIX machine (somehow). The fortran source contains a
|>lot of non-f77 things like structures, unions, records, etc. Is there any
|>way to compile this stuff on a UNIX machine? So far, I'm thinking of
|>adding these VMS fortran extentions to f2c (a fortran to C preprocessor)
|>but I would like to know if anyone has any better ideas first.
|>
|>Thanx, Tom C.
|>

Absoft is marketing something they claim will support all VAX extensions.
There was an article on it in one of the March Open Systems Today issues.


--
Sid VanHouten                svanhout@cmsa.gmr.com (internet)
General Motors Research Labs    (313)986-1958 (phone)
Warren, MI 48090-9055           (313)986-2995 (fax)
Newsgroups: comp.lang.fortran
From: slagle@lmsc.lockheed.com (Mark Slagle)
Subject: Re: Substring assignment -F77 vs F90
Reply-To: slagle@lmsc.lockheed.com
In-reply-to: b_hart@odin.dev.macsch.com's message of 14 Apr 1992 08:52 -0700
Organization: Lockheed Missiles and Space Co., Sunnyvale, Ca.
	<14APR199208524835@odin.dev.macsch.com>
Date: Thu, 16 Apr 92 04:28:46 GMT

In article <14APR199208524835@odin.dev.macsch.com> b_hart@odin.dev.macsch.com (Bill Hart) writes:
   Yes, your code is *illegal* in F77; however, a lot of compilers will let
   this go and also work correctly. I don't remember which compiler forced
   me to rewrite some code that did what you're doing.

----
Since the code is explicitly disallowed by the FORTRAN-77
standard,  there can be no such thing as "work correctly".
The behavior of improper code is undefined in general, and
can certainly be expected to be processor dependent.  Many
compilers will generate machine code for this case without
complaint.  Many compilers are not in conformance.  Using
this illicit code fragment is asking for all the trouble
you will eventually get.

--
----
Mark E. Slagle                                 PO Box 61059
slagle@lmsc.lockheed.com                       Sunnyvale, CA   94088
408-756-0895                                   USA
Newsgroups: comp.lang.fortran
From: taylor@sun.soe.clarkson.edu (Ross Taylor,Peyt312,6652,2655436)
Subject: If you want F90 features do this:
Organization: Clarkson University
Date: Wed, 15 Apr 1992 14:52:52 GMT

If you want your favorite compiler to support F90 features (but don't want
to buy a new compiler) call your compiler maker (not a software 
distributor if thats where you got it from) and tell them what you want.
If you can suggest specific F90 features that they don't have thats a start,
perhaps better than saying I want all of F90 NOW!  Compiler makers
listen to customer demand and if customers demand F90 they will implement
it.  If there is a conspiracy of silence (we all wait for something to happen)
then F90 will be slower in reaching the market.

Ross Taylor

(longing to use F90 but prepared to wait till my compiler supports it - at
least for a while yet).

Xref: sparky comp.lang.fortran:1796 comp.lang.c:7431
From: gdcarson@icaen.uiowa.edu (Gregory Donald Carson)
Newsgroups: comp.lang.fortran,comp.lang.c
Subject: Need math subroutine to...
Date: 10 Apr 92 01:22:09 GMT
Followup-To: comp.lang.fortran
Distribution: usa
Organization: Iowa Computer Aided Engineering Network, University of Iowa
Originator: gdcarson@temp2

Hello Computer and Math Guru's

	I have a problem which I hope someone can help with.  I am transporting
a very large program from VMS to Unix, one of the calls the program makes is to
a VMS FORTRAN math extension named SNLS1 or SNLS1E.  
	This routine calculates and yields the two means from a bimodal 
gaussian distribution.  What is sent to the subroutine is an array of data
points, the length of that array, and several other items of little 
importance.  What the main program expects the subroutine to do is to calculate
the two means from the assumption that the data fits a bimodal gaussian 
distribution.  The program SNLS1 uses the Levenberg-Marquardt method to find
the two means of the data, these are then returned to the program.
	What I am looking for is a program that will accomplish this task.  I
do need to be able to get the code for the program.  Does anyone have any
suggestions on a program to use.  
	Please send responses to me in mail.  Thanks in advance for your help
and for reading my post.

Greg
Newsgroups: comp.lang.fortran
From: jameel@cs.tulane.edu (Akhtar Jameel)
Subject: Help with INCLUDE
Organization: Computer Science Dept., Tulane Univ., New Orleans, LA
Distribution: usa
Date: Fri, 17 Apr 1992 16:31:27 GMT
Nntp-Posting-Host-[nntpd-15017]: rex



i am trying to run someone's fortran code. it has a few INCLUDE statements
at the begining for files called 'PARAMSFL', 'DECLFL' etc. the syntax is

	INCLUDE(PARAMSFL)
	INCLUDE(DECLFL)

i am working with x-editor in CMS on an ibm machine.  the x editor has
to have an extension(file type) to all file names. so all files like
'PARAMSFL' has to be stored as 'PARAMSFL FORTRAN' or 'PARAMSFL DATA'
etc. on compilation i am getting a message saying that the
    INCLUDE(PARAMSFL FORTRAN)    etc

are "INCORRECT NAME".

would someone help me out on this one ???

thanks.
-- 
Akhtar Jameel

INTERNET : jameel@rex.cs.tulane.edu       USENET  : {bionet!}rex!jameel
USmail   : 31 McAlister Drive, Box 1745   Phone   : Office: (504) 483 7456
	   New Orleans, LA 70118                    Home:   (504) 865 9601
Newsgroups: comp.lang.fortran
Subject: Re: PD Fortran Compiler
From: <ATPPH@ASUACAD.BITNET>
Date: Thursday, 9 Apr 1992 09:15:42 MST
Organization: Arizona State University

My experiences with f2c are very good. I had to use
it on a DECstation due to the problem that my code didnt
run with DECfort. f2c compiled it (40000 lines, standard f77:
the code must be portable without changes) without complains
and it run (using -O for cc) without significant performance loss (as
compared to a different version which works with DECfort).
The only problem I found with f2c's library is that the 'F'
format doesnt seem to work, but 'E' and 'D' are OK. The results
did not fully agree with the runs on Crays (cft77) and IBM
RS/6000 (xlf) (which in turn agree to 5-8 digits) but they were in
acceptable limits (C handles arithmetic different than Fortran).
From: charette@cheetah.det.dec.com (Mark Charette)
Newsgroups: comp.lang.fortran
Subject: Re: problems compiling libi77 from f2c under DJGPP
Keywords: f2c DJGPP library
Date: 15 Apr 92 14:10:10 GMT
Reply-To: charette@cheetah.det.dec.com (Mark Charette)
Organization: Digital Equipment Corporation


In article <=kxjb7l.jps@netcom.com>, jps@netcom.com (John Serafin) writes:
|>
|>I can't get several of the libi77 files from f2c to compile under 
|>DJGPP 1.05; 
|> ...
|>Can someone help with this?   There was a recent post saying that there
|>was no problem in the port.   Is there an ftp site with DJGPP forms of
|>the f2c libi77.a and libf77.a ?
|>
|>-- 
|>John P. Serafin  |  Operating a bicycle is more like driving than riding.
|>jps@netcom.com   |  Operating an automobile is more like riding than driving.
|>

I have all the libraries compiled under DJGPP - I'll be happy to provide them
to anyone who asks.
--
Mark Charette                |Yes, I do speak for my employer. Really. Often.
Fisher Engineering Systems   |Digital Equipment Corporation is NOT my employer,
charette@cheetah.det.dec.com |so don't blame them. I just consult there.
Newsgroups: comp.lang.fortran
Subject: Re: Q format specification
From: harper@kauri.vuw.ac.nz (John Harper)
Date: Tue, 7 Apr 1992 21:11:47 GMT
Organization: Victoria University of Wellington, New Zealand

In article <1992Apr7.140117.6858@cfa.harvard.edu> mcdowell@cfa.harvard.edu (Jonathan McDowell) writes:
>From article <11939@tamsun.tamu.edu>, by potter@scan2.tamu.edu (SHANE POTTER):
>> While I am here, does anybody know if the Q specification is unique to VAX
>> fortran or is this some new standard being developed?
>> 
>It's a VAX extension, it is not in the F77 standard and as
>far as I can see it's not in the new F90 standard.

It is however in Silicon Graphics UNIX f77 

John Harper Mathematics Dept. Victoria University Wellington New Zealand
Newsgroups: comp.lang.fortran
From: slagle@lmsc.lockheed.com (Mark Slagle)
Subject: Re: Format of unformatted files: does a standard exist?
Reply-To: slagle@lmsc.lockheed.com
In-reply-to: ercolessi@uimrl7.mrl.uiuc.edu 's message of Sun, 12 Apr 1992 20:20:04 GMT
Organization: Lockheed Missiles and Space Co., Sunnyvale, Ca.
	<BROWNING.92Apr10111016@willard.nas.nasa.gov>
	<1992Apr12.202004.25537@ux1.cso.uiuc.edu>
Date: Mon, 13 Apr 92 22:39:18 GMT

From: ercolessi@uimrl7.mrl.uiuc.edu 
   within character data.  If I am wrong and a general converter can 
   be or has been built, I would be glad to hear about it.

----
It's called FORMATTED I/O.  The whole point of
UNFORMATTED I/O is that you trade portability
for speed.  You get what you pay for.

--
----
Mark E. Slagle                                 PO Box 61059
slagle@lmsc.lockheed.com                       Sunnyvale, CA   94088
408-756-0895                                   USA
Newsgroups: comp.lang.fortran
From: ercolessi@uimrl7.mrl.uiuc.edu 
Subject: Re: Format of unformatted files: does a standard exist?
Reply-To: ercolessi@uimrl7.mrl.uiuc.edu 
Organization: Materials Research Lab
Date: Sun, 12 Apr 1992 20:20:04 GMT

In article <BROWNING.92Apr10111016@willard.nas.nasa.gov>,
browning@willard.nas.nasa.gov (David S. Browning) writes:
|> In article <1992Apr10.151307.28643@e2big.mko.dec.com>
|> lionel@quark.enet.dec.com (Steve Lionel) writes:
|> 
|> <> [ ... background deleted ... ]
|> <>
|> <> "Type A" is comprised of systems which use IEEE "big-endian"
|> <> floating point.  Big-endian means that the most significant bit
|> is
|> <> stored in the lowest addressed byte.  "Type B" is IEEE
|> <> "little-endian", where the most significant bit is in the highest
|> <> addressed byte.  Machines based on Intel x86 processors (eg. IBM
|> PC
|> <> and clones) also use this format, so you can see that the "Type
|> B"
|> <> group is actually quite a bit larger in terms of total number of
|> <> systems than "Type A".
|> <>
|> <> There are three other popular floating point formats: VAX, Cray
|> and
|> <> IBM System/370 (all of these predate the IEEE standard.)

This article did not reach our news server!! Can somebody please forward
me a copy? Thanks!

|> With respect to unformatted I/O, there's more to it than just floating
|> point format.  From the ANSI X3.9-1978 FORTRAN 77 standard, page 12-2,
|> section 12.1.2, "Unformatted Record":
|> 
|>       [ ... paragraph of the standard which says that everything in 
|>             unformatted files is processor-dependent deleted ...]
|> 
|>         [...]          If you want to convert
|> between vendors' unformatted output, you'll need to more than just the
|> binary floating point representation of the machine.
|> 
|> -- David

Sure.  I was just wondering if vendors could agree on an unofficial
"de facto" standard, within the limited but growing subset of
machines with IEEE arithmetics under a Unix or Unix-like operating
system.  As a user, I much appreciate that IBM (on RISCs), Silicon
Graphics, Sun, Hewlett-Packard and Stardent could agree on the
same format, without any official standard forcing them to do so.

Personally, this saved me a lot of conversion work and I would like
to say *THANKS* to the industry for that.  
I only regret that DEC machines, which I also heavily use (and their
coming Alpha machine is very, very promising ...), use a format which
is basically the same, but differs in byte ordering.  This forces
users to do some extra work to exchange data, and it does not
seem possible to build an automatic converter because bytes
within floating point numbers must be swapped, but not bytes
within character data.  If I am wrong and a general converter can 
be or has been built, I would be glad to hear about it.

furio
--
Furio Ercolessi
Materials Research Laboratory           |   Intl School for Advanced Studies
Univ. of Illinois at Urbana-Champaign   |   Trieste, Italy
ercolessi@uimrl7.mrl.uiuc.edu           |   furio@sissa.it
Newsgroups: comp.lang.fortran