HDTenEightyP/NetNews huggingface dataset:
From: walt@netcom.com (Walt Brainerd)
Newsgroups: comp.lang.fortran
Subject: Re: Dynamic Memory Allocation in FORTRAN, Question
Date: 23 Dec 92 00:24:37 GMT
Organization: Netcom - Online Communication Services  (408 241-9760 guest)

>     (1)  FORTRAN 66, FORTRAN 77, and Fortran 90 are all informal
> 	 names.  The official names of the languages are either
> 	 FORTRAN or Fortran.

This is true and one way to account for it is that the accepted
way of writing it changed between standards.
> 
>     (2)  FORTRAN and Fortran are different languages.

I don't think so.  If you buy this, then which language is the
one originally developed by IBM?  They wrote Fortran (and
FORTRAN).
> 
>     (3)  "Standard FORTRAN" does not refer to Fortran 90.

Sure it does.  Some people simply still like the capitalized
way of spelling it, even if it isn't written that way in the
standard.
> 
>     (5)  Fortran 90 has not superceded FORTRAN 77 in the USA.
> 	 The ANSI FORTRAN Standard, X3.9-1978, and the ANSI
> 	 Fortran Standard, X3.198-1992, have coequal status.
> 
Keith already explained why this is not quite right.
I believe that one concrete result of this is that the
X3H5 (formerly Parallel Computing Forum) work was not
approved because it was a binding to Fortran 77.  They
are working on bindings to Fortran 90.

In short, spell it like you want, but to avoid confusing me
and the others who don't really care about these nice
distinctions, use the number.
-- 
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: jsvrc@rc.rit.edu (J A Stephen Viggiano)
Subject: Re: Is FORTRAN a viable language?
Organization: RIT Research Corp
Date: Wed, 30 Dec 1992 22:43:51 GMT
Expires: Fri, 15 Jan 1993 05:00:00 GMT

In article <1hqnn7INNfac@shelley.u.washington.edu> chew@accel.aa.washington.edu (Gilbert Chew) writes:
>Is FORTRAN dead?

Not while I'm Doctor FORTRAN.

>I had always thought that, while C/C++ may be
>getting more publicity, there were still scientists
>and engineers who used FORTRAN.  So, where are
>all the FORTRAN messages?

Did you see the (tounge-in-cheek) thread on Real Programmers? Real Programmers
don't post on the net. :-)

Seriously, I wouldn't equate the volume of net.traffic with the viability
of a language (or anything else, for that matter). I'll admit, C and C++
will probably be around forever. Almost as long as FORTRAN will be.

==Doctor FORTRAN
From: jgd@csd4.csd.uwm.edu (John G Dobnick)
Newsgroups: comp.lang.fortran
Subject: Re: Real Programmers
Date: 27 Dec 1992 08:05:20 GMT
Organization: University of Wisconsin - Milwaukee
Reply-To: jgd@csd4.csd.uwm.edu
NNTP-Posting-Host: 129.89.7.4
Originator: jgd@csd4.csd.uwm.edu

From article <DODD.92Dec16085820@mycenae.cchem.berkeley.edu>, by dodd@mycenae.cchem.berkeley.edu (Lawrence R. Dodd):
> 
> So we have
> 
> 85367 FORMAT(1H 100(3H:-))/1H 23HFOR THE HUMOR-IMPAIRED.)
>       WRITE(6,85367)
> 
> as the final entry in the US and
> 
> 85367 FORMAT(1H 100(3H:-))/1H 24HFOR THE HUMOUR-IMPAIRED.)
>       WRITE(6,85367)
> 
> as the final entry in the England
>  

On a venerable FORTRAN system I once used, the above would result in
the I/O error message "RECORDS EXCEEDING MAXIMUM LENGTH ARE FAULTY".
Why?  The printer (unit 6) is only 132 columns wide.  The FORMAT
specifies a record 301 characters long.  Obviously, something has got to
give.

Oh, an optimization (optimisation?).  Coalesce the 1H 23into 24H FOR...
(or 25H FOR... for you Brits).  Remember, conservation of card columns
and minimization [minimisation] of keystrokes are essential!

Oh, and for the person who suggested typing your program in the
character set of the keypunch (assuming a "commercial" character set
and not the FORTRAN H set), that's for wusses.   Real Programmers
remembered which _physical_ keys produced the proper hole combinations,
and used _those_ keys, ignoring the somewhat "strange" graphics at the
top of the card.  (So what if  ()+'= printed as %^&@# -- _you_ knew
what they really were. [I sure hope I got that translation right --
it's been a while.]  BTW, "^" is really supposed to be the "lozenge"
character, but my ASCII keyboard seems to be lacking that particular
graphic, so... :-).)

Of course, _masochistic_ Real Programmers used the 024 keypunch -- the
one lacking the printer mechanism. :-)


[Point of information: Said "venerable FORTRAN" mentioned above was
FORTRAN V, on a Univac 1108.]

-- 
John G Dobnick                          ATTnet: (414) 229-5727
Computing Services Division             INTERNET: jgd@uwm.edu
University of Wisconsin - Milwaukee     UUCP: uunet!uwm!jgd

"Knowing how things work is the basis for appreciation,
and is thus a source of civilized delight."  -- William Safire
From: ash+@CMU.EDU (Ashvini Sharma)
Newsgroups: comp.lang.fortran
Subject: C -> fortran ?
Date: 3 Jan 93 08:45:23 GMT
Article-I.D.: andrew.cfFnF3G00VpcA89nJW
Organization: Junior, Electrical and Computer Engineering, Carnegie Mellon, Pittsburgh, PA

hi folks,
    does anyone know of a program (public domain or not), which can
translate code written in C to FORTRAN?


thanks a lot,
ash
Newsgroups: comp.lang.fortran
From: eng10317@nusunix1.nus.sg (TAN PONG FEI)
Subject: testing!!!!
Organization: National University of Singapore
X-Newsreader: TIN [version 1.1 PL6]
Date: Mon, 4 Jan 1993 02:47:26 GMT

testing!!!!
From: nick@idacrd.UUCP (Nick Patterson)
Newsgroups: comp.lang.fortran
Subject: Re: Uglifier (was Re: Real Programmers)
Summary: SKOL...
Date: 21 Dec 92 22:53:16 GMT
Organization: idacrd, princeton, nj



<Mortran actually lived on in the Cray world disguised as
<SKOL in the old COS operating system.  At one time, several
<significant pieces of COS were coded in it, including CSP
<(the control statement processor - COS's shell), and some of
<the original debugging tools.  Over time, these were rewritten
<in raw Fortran, CAL (assembler), and Pascal (this was long before
<C became all the rage).

<There was even an undocumented extension in the old CFT Fortran
<compiler called 'IMPLICIT SKOL' which did something magical with
<variables starting with I00.  But this is all dusty history and
<I don't remember what it did.

<No, we didn't port SKOL to Unicos.  :-)

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

I will probably get some perhaps justified
abuse and humiliation for the following:
SKOL was a great preprocessor,
with all sorts of neat features including some
wonderful source code debugging tools.

So I ported it to UNICOS for my own use!

SKOL lives!!

Nick Patterson
nick@ccr-p.ida.org


Newsgroups: comp.lang.fortran
From: maine@altair.dfrf.nasa.gov (Richard Maine)
Subject: DO loops (was: Obscure fortran question)
Organization: NASA Dryden, Edwards, Cal.
Date: Tue, 22 Dec 1992 23:15:08 GMT

On Tue, 22 Dec 1992 22:22:49 GMT, "John C. Ruttenberg" <rutt@paradise.mti.sgi.com> said:

John> Suppose the do variable is assigned above the loop and used in the second
John> expression of a do.  Should its value there be:
John>     1. Its value above the loop, or
John>     2. The value of the first expression in the do?
John> ...
John> Looking at the standard, I was unable to decide what should happen.

Its value above the loop.  Section 11.10.3 of ANSI X3.9-1978 says

    11.10.3 Executing a DO statement.  The effect of executing a DO statement
    is to perform the following steps in sequence:
                                    ^^^^^^^^^^^
      (1) The initial parameter m1, the terminal parameter m2, and the
          incrementation parameter m3 are established by evaluating e1,
          e2, and e3...

      (2) The DO-variable becomes defined with the value of the initial
          parameter m1.

Since the effect must be as if these steps were performed *in sequence*,
the value of the DO-variable used in evaluating e1, e2, and e3 is its
value above the loop.  The value of the DO-variable isn't changed until
step 2.

The same answer applies to f90.

John> The SGI compiler seems to choose option 2.

Then its broken.

--
--
Richard Maine
maine@altair.dfrf.nasa.gov
From: calvin@dinkum.mti.sgi.com (Calvin H. Vu)
Newsgroups: comp.lang.fortran
Subject: Re:  Obscure fortran question
Date: 22 Dec 92 23:02:20 GMT
Organization: Silicon Graphics, Inc.  Mountain View, CA

It's a bug.  I've fixed it in both 3.10.1 and 3.15 release last month.

- calvin
From: gyan@unixg.ubc.ca (Gyan P. Sinha)
Newsgroups: comp.lang.fortran
Subject: Re: graphics in fortran
Date: 29 Dec 92 20:03:06 GMT
Organization: The University of British Columbia
NNTP-Posting-Host: unixg.ubc.ca

In <1992Dec29.113206.9790@ac.dal.ca> jpeach@ac.dal.ca writes:

>I am going to be writing  a program in fortran that is going
>to require some basic graphics ability.  What I want to be able
>to do is to draw some line graphics in two dimensions.  I am
>finding it difficult to locate a tool that woill add me in doing
>this in fortran.  It has be be some type of standard so that
>the software can be compiled on the IBM PC, MAC and the VMS
>computers.  I discovered there is a standard called GKS
>(Graphics Kernaling System)  It will do everything that I want
>it to but I cannot find a company that sells it.  Can anyone
>tell me were I can get this software tool or any other tools
>that will work.  Please e-mail me at JPEACH@ac.dal.ca or
>post a message here.  Thanks.
> 
> 
>///MiStEr pEaCh\\\


Watfor-77 by Watcom does have GKS. It's not a 32 bit compiler, so your
code and data will have to be small. Their address is:

Watcom
415 Phillip Street
Waterloo, Ontario
Canada N2L 3X2
Tel: (519) 886-3700
FAX: (519) 747-4971


Hope this helps.

Gyan P. Sinha
UBC, Vancouver.
Newsgroups: comp.lang.fortran
From: jot@cray.com (Otto Tennant)
Subject: Re: Uglifier (was Re: Real Programmers)
Date: 21 Dec 92 09:24:40 CST

wws@craywr.cray.com (Walter Spector) writes:

>In article<1992Dec18.233525.19273@nsisrv.gsfc.nasa.gov>,knox@spruce.gsfc.nasa.gov (Robert Knox) writes:
>> Re. output from Mortran:
>>
>> On my first largish Fortran projects I used a pre-processor 
>> call FLECS, for CDC 170 series machines.

>Mortran actually lived on in the Cray world disguised as
>SKOL in the old COS operating system.
>[... deletions ...]

>There was even an undocumented extension in the old CFT Fortran
>compiler called 'IMPLICIT SKOL' which did something magical with
>variables starting with I00.  But this is all dusty history and
>I don't remember what it did.

It is equivalent to 'IMPLICIT NONE', but allowing implicit integer
declaration of variables beginning I00.

When you look inside SKOL (I recommend Dramamine first), it appears
to be based on STAGE2, from the early 70's at U of Colorado.

>No, we didn't port SKOL to Unicos.  :-)

>Walt
>----
>Walt Spector
>(wws@renaissance.cray.com)
>Sunnyvale, California
>_._ _._ _.... _. ._.
--
===============================================================================
J.Otto Tennant      Forsan et haec olim meminisse juvabit.         jot@cray.com
Cray Research, Inc.              Virgil                          (612) 683-5872
655 Lone Oak Drive                                                
Newsgroups: comp.lang.fortran
From: walt@netcom.com (Walt Brainerd)
Subject: Re: Dynamic Memory Allocation in FORTRAN, Question
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Date: Mon, 21 Dec 1992 17:29:31 GMT

In article <BzL8tz.H5u@news.cso.uiuc.edu>, ercolessi@uimrl3.mrl.uiuc.edu (furio ercolessi) writes:
> In article <1992Dec20.233539.4905@sol.ctr.columbia.edu>, shenkin@still3.chem.columbia.edu (Peter
> Shenkin) writes:
> |>In article <Dec.20.02.22.20.1992.7312@spade.rutgers.edu>
> |> xiong@spade.rutgers.edu (Xiong) writes:
> |>>Hi, I am wondering if it is possible to allocate memory dynomically in
> |>>FORTRAN as in C? 
> |>
> |>No.
> 
> We are a bit negative, aren't we?  :-)
> 
> Well, if you stick to the FORTRAN standard the answer is no
> [of course, Fortran is another story].

THE programming language Fortran has sometimes been written
"Fortran" (the way it appeared in the first IBM manuual for
the IBM 704) and sometimes been written "FORTRAN".  There has
been a trend to adopt "Fortran" since about 1978, just after
the Fortran 77 standard came out.  The point is that the
way of writing the word does NOT indicate the version.
Saying that standard FORTRAN does not have dynmaic storage
allocation, but standard Fortran does is very confusing.

Fortran 77 is still an American standard, but for the rest
of the world, there is only one standard, Fortran 90, and
of course it does have dynamic storage allocation.

Fortran 77 is still an American standard, but for the rest
of the world, there is only one standard, Fortran 90, and
of course it does have dynamic storage allocation.
-- 
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: b259phl@utarlg.uta.edu (PHILIP LIPPEL)
Subject: Re: Is FORTRAN a viable language?
News-Software: VAX/VMS VNEWS 1.41    
Organization: The University of Texas at Arlington
Date: Thu, 31 Dec 1992 01:02:00 GMT

In article <30DEC92.23333933@edison.usask.ca>, f54oguocha@edison.usask.ca writes...
> 
>>Is FORTRAN dead?
>> 
>>I had always thought that, while C/C++ may be
>>getting more publicity, there were still scientists
>>and engineers who used FORTRAN.  So, where are
>>all the FORTRAN messages?

A very large fraction of the EXISTING code for scientific applications is in
FORTRAN. This alone will assure its importance for some time to come. Which 
language you choose for new applications is another (religious) matter alto-
gether, of course.
From: khb@chiba.Eng.Sun.COM (Keith Bierman fpgoup)
Newsgroups: comp.lang.fortran
Subject: Re: Looking for MATRIX X
Date: 22 Dec 92 17:37:25
Organization: SunPro
Distribution: world
NNTP-Posting-Host: chiba
In-reply-to: frzmtdb@aspentec.com's message of 22 Dec 92 16:22:44 EST


In article <1992Dec22.162244.886@aspentec.com> frzmtdb@aspentec.com writes:
 

   Hi.
   I'm looking for a package (probably fortran) called "matrix x".
   It is used for control system design.

   Does anyone know who the vendor of this package (or similar packages)
   is?  I think it used to be a firm in Palo ALto, called Industrial 
   Systems???  but this is somewhat dated information.


ISI
800 675 MATH or 408 980 1500

Santa Clara, not Palo Alto (at least, these days).
--
----------------------------------------------------------------
Keith H. Bierman    keith.bierman@Sun.COM| khb@chiba.Eng.Sun.COM
SunPro 2550 Garcia MTV 12-40             | (415 336 2648) fax 964 0946
Mountain View, CA 94043  <speaking for myself, not Sun*> Copyright 1992

Newsgroups: comp.lang.fortran
From: "John C. Ruttenberg" <rutt@paradise.mti.sgi.com>
Subject: Obscure fortran question
Reply-To: rutt@paradise.mti.sgi.com
Organization: Silicon Graphics, Inc.  Mountain View, CA
Date: Tue, 22 Dec 1992 22:22:49 GMT



Suppose the do variable is assigned above the loop and used in the second
expression of a do.  Should its value there be:

    1. Its value above the loop, or

    2. The value of the first expression in the do?

This is the same as the question of wheter the control variable and the final
bound are initialized in parallel or serially.  Looking at the standard, I was
unable to decide what should happen.

The SGI compiler seems to choose option 2.  Here's a test that demonstrates
this.

      count = 0
      i = 10
      do 240 i = 1, identity(i)
240     count = count + 1
      print *, count, i
      stop
      end

      integer function identity(i)
      integer i

      identity = i

      return
      end

This prints:

            1           2

demonstrating that i had a value of 1 (not 10) at the time of the call to
identify?  Is this right?
From: corbett@lupa.Eng.Sun.COM (Robert Corbett)
Newsgroups: comp.lang.fortran
Subject: Re: Dynamic Memory Allocation in FORTRAN, Question
Date: 22 Dec 1992 06:06:41 GMT
Organization: Sun
NNTP-Posting-Host: lupa

In article <BzMK05.HJ2@news.cso.uiuc.edu> ercolessi@uimrl3.mrl.uiuc.edu (furio ercolessi) writes:
>In article <1992Dec21.172931.15093@netcom.com>, walt@netcom.com (Walt Brainerd) writes:
>>In article <BzL8tz.H5u@news.cso.uiuc.edu>, ercolessi@uimrl3.mrl.uiuc.edu (furio ercolessi) writes:
>|>> Well, if you stick to the FORTRAN standard the answer is no
>|>> [of course, Fortran is another story].
>|>
>|>THE programming language Fortran has sometimes been written
>|>"Fortran" (the way it appeared in the first IBM manuual for
>|>the IBM 704) and sometimes been written "FORTRAN".  There has
>|>been a trend to adopt "Fortran" since about 1978, just after
>|>the Fortran 77 standard came out.  The point is that the
>|>way of writing the word does NOT indicate the version.
>|>Saying that standard FORTRAN does not have dynmaic storage
>|>allocation, but standard Fortran does is very confusing.
>
>Ooops! Sorry. Then I misinterpreted a discussion here some weeks 
>ago. I will always add the number, promised!

You did not misunderstand.  The introduction to ISO/IEC 1539:1991(E)
states

    Note that the name of this language, Fortran, differs from that
    in FORTRAN 77 in that only the first letter is capitalized.
    Both FORTRAN 77 and FORTRAN 66 (by which the authors mean the
    standards for those languages, -rpc) used only capital letters
    in the official name of the language, but Fortran 90 does not
    continue that tradition.

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.

    (2)  FORTRAN and Fortran are different languages.

    (3)  "Standard FORTRAN" does not refer to Fortran 90.

    (4)  Standard FORTRAN could be used to refer to FORTRAN 66,
	 save that FORTRAN 77 superceded it.

    (5)  Fortran 90 has not superceded FORTRAN 77 in the USA.
	 The ANSI FORTRAN Standard, X3.9-1978, and the ANSI
	 Fortran Standard, X3.198-1992, have coequal status.

						Yours truly,
						Robert Corbett
From: c79057@petek.tek.st.statoil.no (Joergen Leiknes)
Newsgroups: comp.lang.fortran
Subject: How to detect format overflow
Date: 22 Dec 92 14:01:11 GMT
Reply-To: c79057@petek.tek.st.statoil.no (Joergen Leiknes)
Organization: Statoil

I want to detect overflow in format statements, to avoid to have
asterisks in the produced output. (Yes,I know that it is possible
to have larger fields for each variable, but it would be nice to
have an error jump when such things occur)

In the little test program below:
      PROGRAM IOTEST
      INTEGER ISTAT, I
      REAL X
      X = 123123.3
      I = -123123
      WRITE(*,700,ERR=900, IOSTAT= ISTAT) X, I
700   FORMAT(' X is ',F6.3,' I is ',I6)
      GOTO 999

900   CONTINUE
      WRITE(*,*) ' IOERROR no. ', ISTAT
      GOTO 999

999   CONTINUE
      END

Gives this output:
 X is ****** I is ******

and no error is catched.

I would like to know if it is possible according to f77 or f90 standard
to catch such overflows.

Thanks in advance
Jorgen Leiknes, Statoil NORWAY
Newsgroups: comp.lang.fortran
From: dnl@convex.is.macsch.com (David Lombard)
Subject: Re: Obscure fortran question
Organization: MacNeal-Schwendler Corp.
Date: Wed, 23 Dec 92 22:46:08 GMT

In article <tubetf0@sgi.sgi.com> rutt@paradise.mti.sgi.com writes:
>
>
>      i = 10
>      do 240 i = 1, identity(i)
>

In my reading, the value of the expression `identity(i)' should be
determined _before_ the DO-variable is defined.  See 11.10.3 (pg 11-7):

	11.10.3 Executing a DO statement.  The effect of executing
	a DO statement is to perform the following steps in
	sequence:

	   (1)	The initial parameter m1, the terminal parameter m2,
		and the incrementation parameter m3 are established
		by evaluating e1, e2, and e3, respectively,
		including, if necessary, conversion to the tyupe of
		the DO-variable according to the rules...

	   (2)	The DO-variable becomes defined with the value of the
		initial parameter m1.

	   (3)	The iteration count is established and is the value 
		of the expression

		...

So, since step (1), the evaluation of the control parameters, must 
precede step (2), the assignment of the DO-variable, identity(10)
should have been executed in step (1).

Regards,
DNL

                 MY_COMMENTS = MY_OPINIONS = NOBODY_ELSES;

David N. Lombard    The first thing we do,         The MacNeal-Schwendler Corp
dnl@macsch.com      Let's kill all the lawyers.    815 Colorado Blvd
(213) 259-4911      II Henry VI, IV.ii             Los Angeles, CA  90041
From: dodd@mycenae.cchem.berkeley.edu (Lawrence R. Dodd)
Newsgroups: comp.lang.fortran
Subject: Re: WANTED URGENTLY!!PLEASE!!
Date: 21 Dec 92 08:48:11
Organization: Dept of Chemical Engineering, Polytechnic Univ, NY, USA
	<mac.724867277@depot.cis.ksu.edu.cis.ksu.edu>
NNTP-Posting-Host: mycenae.cchem.berkeley.edu
In-reply-to: mac@cis.ksu.edu's message of 20 Dec 92 15:26:26 GMT


>>>>> "Myron" == Myron A. Calhoun <mac@cis.ksu.edu> writes:

>My sister is doing a Fortran77 project on the game Othello. Our command
>of the Fortran language is not powerful enough to write a good program.
>Since this project will take up 50% of her final examinations, she is
>very worried right now. Can anyone send a sample of the algorithm to
>rescue her? Please send to either ....

  Myron> I'm bothered by this request, but maybe I just don't understand.

I think you understand all too well.

  Myron>     If this were the situation, I don't understand why the URGENT
  Myron>     request for an algorithm for the game of Othello.

It's probably `URGENT' because she didn't start on it until it was too late.

I laugh whenever I see postings like the original.  It is equivalent to
someone in English Literature posting a request for a term paper.

Newsgroups: comp.lang.fortran
From: dil@mace.cc.purdue.edu (Perry G Ramsey)
Subject: Re: Common block problem with MS-FORTRAN
Keywords: segment boundaries common block
Organization: Purdue University, Department of Earth and Atmospheric Sciences
Distribution: world,local
Date: Thu, 31 Dec 1992 19:17:49 GMT

In article <29DEC199220562573@osprey.telcom.arizona.edu> doug@osprey.telcom.arizona.edu (Doug Wellington USGS) writes:

>I am trying to convert a program from UNIX to MS-DOS.  The program
>compiles fine on a SPARC 1+, but I can't get it to compile on a 486
>DOS box using Microsoft FORTRAN 4.01 or 5.0.  I get the same message
>with either one:

>actrep.for(21) : error F2379: DESCRI : item in common block crosses segment
>actrep.for(333) : error F2379: DESCRI : item in common block crosses segment

5.1 has the /Gt option that forces all varaibles above a certain size into
their own segment.  Maybe that has something to do with it?
-- 
Perry G. Ramsey         Department of Earth and Atmospheric Sciences
dil@mace.cc.purdue.edu  Purdue University, West Lafayette, IN USA
perryr@purccvm         
N9LFF                   "Jest not with a craven duck."
Newsgroups: comp.lang.fortran