HDTenEightyP/NetNews huggingface dataset:
From: taylorr@debussy.cs.unc.edu (Russell Taylor)
Newsgroups: comp.lang.fortran
Subject: Re: Unix ARGC,ARGV in Fortran 77
Date: 18 Aug 92 12:26:39 GMT
Organization: The University of North Carolina at Chapel Hill

In article <14542@borg.cs.unc.edu> marshall@marshall.cs.unc.edu (Jonathan A. Marshall) writes:
>I need to write a Fortran program that will accept command-line arguments.
>I'm running Ultrix f77 on a DECstation 5000.  In C, command-line arguments
>can be passed with argc and argv.
>
>How is this done in f77?  There's got to be a way, right?
>
	"man -k arg" on tyrosine reveals:
getarg, iargc (3F)      - return Fortran command-line argument
	On the decstation there are no such man pages, so here are the
tyrosine versions.  Note that tyrosine (iris) is a System V unix, so
who knows if they are the same?

GETARG(3F)                     Silicon Graphics                     GETARG(3F)

NAME
     getarg, iargc - return Fortran command-line argument

SYNOPSIS
     character*N c
     integer i, j
     integer function iargc

     call getarg(i, c)
     j = iargc()

DESCRIPTION
     getarg returns the i-th command-line argument of the current process.

     iargc returns the index of the last argument.

          foo arg1 arg2 arg3

     getarg(2, c) would return the string ``arg2'' in the character variable
     c.

     iargc would return 3 as the value of the function call.

SEE ALSO
     getopt(3C).

NOTES
     The compiler expects the existence of a Fortran MAIN_ program when these
     functions are used.

ORIGIN
     AT&T V.3

Page 1                          Release 4.0.1                      August 1991


GETARG(3F)                     Silicon Graphics                     GETARG(3F)

NAME
     getarg, iargc - return Fortran command-line argument

SYNOPSIS
     character*N c
     integer i, j
     integer function iargc

     call getarg(i, c)
     j = iargc()

DESCRIPTION
     getarg returns the i-th command-line argument of the current process.

     iargc returns the index of the last argument.

          foo arg1 arg2 arg3

     getarg(2, c) would return the string ``arg2'' in the character variable
     c.

     iargc would return 3 as the value of the function call.

SEE ALSO
     getopt(3C).

NOTES
     The compiler expects the existence of a Fortran MAIN_ program when these
     functions are used.

ORIGIN
     AT&T V.3

Page 1                          Release 4.0.1                      August 1991


-- 
He who follows a path perpetuates that path.
Practice random kindness and sensless acts of beauty.
From: burley@geech.gnu.ai.mit.edu (Craig Burley)
Newsgroups: comp.lang.fortran
Subject: Re: gnu-fortran
Date: 13 Aug 92 21:02:16 GMT
Organization: Free Software Foundation 545 Tech Square Cambridge, MA 02139
In-reply-to: ce1zztw@prism.gatech.EDU's message of 25 Jul 92 04:32:05 GMT

In article <64323@hydra.gatech.EDU> ce1zztw@prism.gatech.EDU (Tommy Barr) writes:

       I did not see a faq, but is there a gnu version of fortran
       or anything similar available.

GNU Fortran is nearing alpha testing.  To get status updates on it prior to
an announcement of the first public (beta) release, send email to this
address to get on the GNU Fortran Mailing List:

    info-gnu-fortran-request@prep.ai.mit.edu
--

James Craig Burley, Software Craftsperson    burley@gnu.ai.mit.edu
Member of the League for Programming Freedom (LPF)
Newsgroups: comp.lang.fortran
From: system@alchemy.chem.utoronto.ca (System Admin (Mike Peterson))
Subject: Re: Does your f77 compiler accepts this?
Organization: University of Toronto Chemistry Department
Date: Sat, 22 Aug 1992 14:18:31 GMT

In article <2873@tansei1.tansei.cc.u-tokyo.ac.jp> mhiroshi@tansei.cc.u-tokyo.ac.jp (H. Murakami) writes:
>      X = 1.0
>      WRITE(*,*) (X)
>      END

The HP-UX 8.07 f77 does.
-- 
What are the chances that any computer system will ever "work" properly?
... and Slim just left town. -*- Mike Peterson, SysAdmin, U/Toronto Chemistry
From: bauwens@acs.ucalgary.ca (Luc Bauwens)
Newsgroups: comp.lang.fortran
Subject: Re: Where one can find a book on Microsoft Fortran?
Date: 17 Aug 92 15:30:28 GMT
Distribution: usa
Organization: The University of Calgary, Alberta

In article <1992Aug17.004338.19871@wam.umd.edu> qian@wam.umd.edu (Yong Qian) writes:
>I am looking a book on Microsoft Fortran (5.0). However, looking at local
>book stores, I can hardly find any book on Fortran, none on MS Fortran. 
>I was just wondering if there are many people using Fortran on a PC. The
>C and Pascal books are full of bookshelfs in those stores.

I would think that any book on Fortran, plus the Microsoft manual,
should be more than enough. 

It's true that on some respects (such as mixed-lannguage), the manuals
aren't that great, but your typical book on this or that software
product isn't usually any better.

Luc B
Newsgroups: comp.lang.fortran
From: cflatter@nrao.edu (Chris Flatters)
Subject: Re: how to quit on an NaN result?
Reply-To: cflatter@nrao.edu
Organization: NRAO
Date: Mon, 17 Aug 1992 22:28:20 GMT

In article 21922@ultb.isc.rit.edu, jsvrc@rc.rit.edu (J A Stephen Viggiano) writes:
>A portable way is to use an internal write. Write a known NaN to
>a character variable, use the substring that flags the result as a NaN.
>Then, write the value you want to test to another character variable, and
>compare *these* variables.
>

This is unsafe.  A floating point implementation that conforms to IEEE-754
must support at least two different NaN bit patterns (one signalling NaN
and one non-signalling NaN) for each supported precision.

	Chris Flatters
	cflatter@nrao.edu




Newsgroups: comp.lang.fortran
From: davem@ee.ubc.ca (david michelson)
Subject: Re: programming style question
Organization: University of BC, Electrical Engineering
Date: Mon, 17 Aug 1992 17:02:54 GMT

Thank you to all who replied to my question regarding saving variables
within a subroutine between invocations and drew my attention to the SAVE
statement.  Much appreciated.  
 
This really points out the need for programming texts that fall somewhere
between "10 statement Introductory Fortran" and the ANSI standard. If
anyone would care to recommend any books on programming style in Fortran, 
I would be most interested.  Does a FAQ list exist for this group?  If so,
is such a list included?
 
Dave Michelson  "davem@ee.ubc.ca"
From: dodson@convex.COM (Dave Dodson)
Newsgroups: comp.lang.fortran
Subject: Re: Ignoring Least Significant Bit in a Real Compare
Date: 21 Aug 92 21:22:25 GMT
Reply-To: dodson@convex.COM (Dave Dodson)
Organization: Engineering, CONVEX Computer Corp., Richardson, Tx., USA
Originator: dodson@bach.convex.com
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.

In article <1992Aug21.203055.29668@aero.org> wae@aero.org (William A. Emanuelsen) writes:
>I am working on a 60-bit CDC machine in fortran-4.  (stop laughing!) I
>am trying to compare two real numbers with .EQ. in an 'if' statement.  
>But what happens is that the numbers I am comparing, and which should be 
>equal, fail the test since the 60th bit sometimes gets rounded in the 
>opposite direction.
>
>So what I did was to write a logical function, REQ, to replace the .EQ. 
>comparison:
>
>      LOGICAL FUNCTION REQ(X1,X2)
>C
>      REQ = .FALSE.
>      IF (ABS(X1-X2) .LT. EPS) REQ = .TRUE.
>      RETURN
>      END
>
>Where EPS is the smallest difference I expect to see between two numbers 
>that actually are unequal.
>
>So where I formerly had: IF (TEMP1 .EQ. TEMP2) ...
>I now have:              IF (REQ(TEMP1,TEMP2)) ...
>
>Is there a better (faster and more straightforward) way to ignore the 
>least significant bit when doing real compares in fortran-4?
>(Bit-shifting seems to add more steps.)

I would do something such as the following in hopes of eliminating EPS.

      LOGICAL FUNCTION REQ(X1,X2)
C
      T = X1 + 0.5 * (X2-X1)
      REQ = X1 .EQ. T .OR. X2 .EQ. T
      RETURN
      END

The idea is that if X1 and X2 are adjacent numbers, then the midpoint will
have to be equal to one of the numbers.  If there are enough numbers between
X1 and X2, X3 will not equal either of X1 and X2.  Only some testing will
show what happens when X1 and X2 have only one or two numbers between them.

I doubt if this code is faster than yours, but it may work better over a
range of values of X1 and X2.

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

Dave Dodson		                             dodson@convex.COM
Convex Computer Corporation      Richardson, Texas      (214) 497-4234
From: asupowit@magnus.acs.ohio-state.edu (Aaron Supowit)
Newsgroups: comp.lang.fortran
Subject: Re: Why CALL EXIT? (was Re: Question for C ==> Fortran)
Date: 3 Aug 92 19:38:10 GMT
Organization: The Ohio State University

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?
>
>(At least there aren't many codes twiddling 'sense lights' anymore. :-)
>
>Walt
>-- 
>Walt Spector
>(wws@renaissance.cray.com)
>Sunnyvale, California
>_._ _._ _.... _. ._.

 Originally STOP stop stopped the cpu (not the current program). Therefore many installations
(such as the one where I was employed) prohibitted its use. CALL EXIT was a way to 
terminate a program gracefully. With the advent of multi-programming environments, the 
STOP statement's function was of necessity changes. To insure compatibility with old, existing
programs, CALL EXIT was kept. People still use it because old habits die hard. I still
see many things done which are old, old habits.

  Aaron Supowit - Ohio State University.
From: khb@chiba.Eng.Sun.COM (Keith Bierman fpgroup)
Newsgroups: comp.lang.fortran
Subject: Re: programming style question
Date: 16 Aug 92 20:19:04 GMT
Organization: Sun MegaSystems
NNTP-Posting-Host: chiba
In-reply-to: davem@ee.ubc.ca's message of Sun, 16 Aug 1992 22:17:25 GMT


>    Is it dangerous or poor practice to assume that the variables

A careful reading of the standard will reveal that this is indeed,
poor practice.

If you wish to have a variable retain its old value across
invokations, you must use the 

	SAVE foo

or the blanket
	
	SAVE

in the function/subroutine you wish to behave in this fashion. Of
course, putting the variable in COMMON 	(so long as the COMMON is
always in scope, typically part of your main program) is equally safe.

This is, in fact, why the SAVE command exists.
--
----------------------------------------------------------------
Keith H. Bierman    keith.bierman@Sun.COM| khb@chiba.Eng.Sun.COM
SunPro 2550 Garcia MTV 12-33             | (415 336 2648) fax 964 0946
Mountain View, CA 94043  <speaking for myself, not Sun*> Copyright 1992
From: LJM@SLACVM.SLAC.STANFORD.EDU (Len Moss)
Newsgroups: comp.lang.fortran,slac.lang.fortran
Subject: Re: What is the name of the latest Fortran standard document?
Date: 14 Aug 92 17:51:30 GMT
Organization: Stanford Linear Accelerator Center

In article <1992Aug14.073329.21922@bnr.ca>, davisonj@bnr.ca (John Davison) says:
>        I am sitting here with Draft S8, Version 112 of S8 (X3.9-198x), also
>known as X3J3/S8.112, and I am wondering if this document actually represents
>the new Fortran...

X3J3/S8.112 is an earlier draft of what has now become Fortran 90.  The draft
that was eventually approved was S8.118, I believe.  At present (August 1992),
only the international standard has been published (the identical US standard
still (!) is hung up by procedural problems).  The official designation for
the standard is ISO/IEC 1539:1991.  I believe it can be ordered through ANSI
(1430 Broadway; New York, NY 10018), but it can also be obtained directly from
the ISO Secretariat at considerable savings (the ISO price, last I heard, came
out to about US $120); the address is:

                    ISO
                    1, rue de Varembe
                    Case postale 56
                    1211 Geneva 20
                    SWITZERLAND
                    (Fax: +41 22 734 10 79)

--
Leonard J. Moss <ljm@slac.stanford.edu>   | My views don't necessarily
Stanford Linear Accelerator Center, MS 97 | reflect those of SLAC,
Stanford, CA   94309                      | Stanford or the DOE
From: ecm9093@aston.ac.uk (J.P.FLETCHER)
Newsgroups: comp.lang.fortran
Subject: Re: Fortran subroutine in C main
Date: 18 Aug 92 12:09:13 GMT
Distribution: comp.lang.fortran
Organization: Aston University

In article <JAAKSI.92Aug18133546@korppi.cs.tut.fi> jaaksi@cs.tut.fi (Jaaksi Ari) writes:


>Hi!

>How to use Fortranm subroutines called from C main. Everything
>else seems to be OK except when some IO -routines occur in
>Fortran subroutines. Is there any way to handle these problems.
>All kind of info is more than welcome.

>Ari Jaaksi
>-- 
What system are you using?
--------------------------------------------------------------
Dr John P. Fletcher       
Department of Chemical Engineering and Applied Chemistry,
Aston University,         Tel: (44) 21 359 3611 ext 4625
Aston Triangle,		  Email(Janet): J.P.FLETCHER@UK.AC.ASTON
BIRMINGHAM B4 7ET   U.K.  Email(Other): J.P.FLETCHER@ASTON.AC.UK
--------------------------------------------------------------
Newsgroups: comp.lang.fortran
From: sichermn@beach.csulb.edu (Jeff Sicherman)
Subject: Fortran routines to emulate COBOL PICTURE editing
Organization: Cal State Long Beach
Date: Fri, 21 Aug 1992 06:36:19 GMT

  Looking for fortran routines to emulate COBOL-like output PICTURE
editing. That is, given a string with +'s, -'s, *'s and similar
fixed or floating filler characters and actual (.) or implied (V)
decimal point, will take an integer or real operand an produce an
output character string with the number formatted according to the
'picture' of it. Must be generic enough fortran to be ported to
various compilers and o/s's, not just a proprietary routine that
happens to be implemented on a particular system. Calls to other-
language implementations are similarly unacceptable unless source
is available for THEM.

   Thanks for any help.


-- 
Jeff Sicherman
up the net without a .sig
Newsgroups: comp.lang.fortran
From: dubuf@sicsun.epfl.ch (Hans DU BUF)
Newsgroups: comp.lang.fortran
Subject: Re: Ultrix Fortran alternatives?
Date: 13 Aug 92 10:21:12 GMT
Organization: Ecole Polytechnique Federale de Lausanne

In article <1992Aug11.210101.10249@nmt.edu>, dcuddihy@nmt.edu (David Cuddihy) writes:
|> 
|> 	We are currently running with the Fortran that came with the Ultrix 4.2
|> release and we have had troubles with inconsistencies, for example code that
|> runs on our Suns, miscellaneous workstations at other sites, supercomputer
|> machines, etc... don't compile or have slightly different functionality on
|> the Ultrix f77(and occasionally vice-versa).
|> 	Since we are trying to write generic code, we aren't too interested in
|> how to get it to run on the Ultrix(and hence not on all of the other machines)
|> Instead we were wondering what other Fortran compilers there are out there...
|> (If there was something public domain that could be imported via ftp, that'd
|> be ideal!)
|> 
|> 
|> 				Thanks in advance,
|> 					-Dave

Does f77 mean the K&R portable compiler? I had some problems too, one was
that I could not write to internal files. A pain.
But now we have the ULTRIX FORT compiler, which is, as far as I can see,
completely equivalent to the VMS compiler, and the sources can be compiled
on any machine (sun, sg, cray, maspar, cm).
One small problem was that the old Silicon Graphics f77 did not accept
line comments starting with a !, but the new version does now.
Hans
From: sla@fast.ucsc.edu (Steve Allen)
Newsgroups: comp.lang.fortran
Subject: Re: Fortran 90:  Pointers to Functions?
Date: 14 Aug 1992 17:04:55 GMT
Organization: UCO/Lick Observatory
NNTP-Posting-Host: fast.ucsc.edu
Summary: It does not have them, what can be done?
Keywords: missing feature!

In article <1693l7INNn4o@darkstar.UCSC.EDU> sla@fast.ucsc.edu I wrote:
>[Fortran 77 & 90 do not have anything like C's "pointer to a function"]
>Is there some other (reasonably elegant) method for getting this kind of
>functionality in Fortran 90?

This is an example of what I would like to be doing with pointers to functions

First, the "FORTRAN way", which seems somewhat inelegant
	IF     (STATE .EQ. KNOWNSTATE(1)) THEN
	    CALL FUNC1
	ELSEIF (STATE .EQ. KNOWNSTATE(2)) THEN
	    CALL FUNC2
C       ...     about 900 lines of mindless code later ...
	ELSEIF (STATE .EQ. KNOWNSTATE(459)) THEN
	    CALL FUNC459
	ELSE
	    CALL REPORT_UNKNOWN_STATE(STATE)
	ENDIF

Then, the thing that I would like to be able to do, which can be expressed
in many fewer lines of code.
	SUCCESS = .FALSE.
	I = 0
100     CONTINUE
	IF (.NOT. SUCCESS) THEN
	    IF (I .LT. 459) THEN
		I = I + 1
		IF (STATE .EQ. KNOWNSTATE(I)) THEN
		    CALL {the Ith function, we have no syntax for this}
		    SUCCESS = .TRUE.
		ENDIF
		GOTO 100
	    ELSE
		CALL REPORT_UNKNOWN_STATE(STATE)
	    ENDIF
	ENDIF

Furthermore, with some kind of array of pointers to functions, I could
exchange one function in the array for another during the execution of
the program.  Basically, the user pushes some button, and the program
starts behaving differently because it is calling different functions
in response to the user's input.

Now for today's questions:

1)
Is there some much better way I could do this within Fortran 77 and/or 90?

2)
There are lots of good (and bad) examples of complicated user interfaces in C,
and there are even tools for building user interfaces in C.
Are there any good examples, reference books, tools for building complicated
user interfaces in Fortran?  (I am hoping for any hints which help the
programmer to avoid the nearly mindless repetition demonstrated in the
first example code.)
_______________________________________________________________________________
Steve Allen          | That was the equation!         |   sla@helios.ucsc.edu
UCO/Lick Observatory | Existence!...Survival must     | If the UC were opining,
Santa Cruz, CA 95064 | cancel out programming! -- Ruk | it wouldn't tell me.
From: qian@wam.umd.edu (Yong Qian)
Subject: Where one can find a book on Microsoft Fortran?
Organization: Workstations at Maryland, University of Maryland, College Park
Distribution: usa
Date: Mon, 17 Aug 1992 00:43:38 GMT

I am looking a book on Microsoft Fortran (5.0). However, looking at local
book stores, I can hardly find any book on Fortran, none on MS Fortran. 
I was just wondering if there are many people using Fortran on a PC. The
C and Pascal books are full of bookshelfs in those stores.
From: khb@chiba.Eng.Sun.COM (Keith Bierman fpgroup)
Newsgroups: comp.lang.fortran
Subject: Re: how to quit on an NaN result?
Date: 16 Aug 92 14:31:41
Organization: Sun MegaSystems
NNTP-Posting-Host: chiba
In-reply-to: Bruce.Scott@bbs.oit.unc.edu's message of 16 Aug 92 20:08:37 GMT


>        if (avar .eq. 'NaN') stop

You don't mention your environment. Clearly it isn't incorporated in
the ANSI X3.9-1978 nor the ISO 1539:1991 standards.

If you are running on a Sun, using the SunPro compiler, the "obvious"
choices are

	f77 $your_favorite_options -fnonstd *.f

The fnonstd changing the way underflow works and trapping rather than
ignoring "ieee exceptions". Since I personally want proper underflow,
I'd go with

	i=ieee_handler("set","common",%val(2)) 

where %val(2) is the magic number for causing SIGFPE_ABORT to occur. 

Or, you can test individual numbers via the 

     int isnan(x)

function from libm. This provides the most control, but requires the
most work.

See the Numerical Computation Guide for more details about these
approaches. In addition the FORTRAN User's Guide and the various man
pages can be helpful.

If you are coding in another environment, milage may vary.
--
----------------------------------------------------------------
Keith H. Bierman    keith.bierman@Sun.COM| khb@chiba.Eng.Sun.COM
SunPro 2550 Garcia MTV 12-33             | (415 336 2648) fax 964 0946
Mountain View, CA 94043  <speaking for myself, not Sun*> Copyright 1992

Newsgroups: comp.lang.fortran
From: jtbell@hubcap.clemson.edu (Jon Bell)
Subject: Re: programming style question
Organization: Presbyterian College, Clinton SC
Date: Mon, 17 Aug 1992 01:37:14 GMT

In article <1992Aug16.221725.6760@ee.ubc.ca> davem@ee.ubc.ca (david michelson) writes:
> 
>    Is it dangerous or poor practice to assume that the variables
>    in a subroutine will retain the values assigned in the immediately
>    previous execution the next time it is called?
>

[example deleted]

Yes, it is dangerous to assume this.  With most compilers, it will work OK,
but on _some_ systems, local variables in a subroutine will get thrown away
when you return to the calling routine.  It depends on whether local
variables are allocated as static storage, or on a "run-time stack."

It may work fine on your current machine, but it you port the code to another
machine, you run the risk that the code will fail.

Fortunately, there's an easy solution.  Simply put a SAVE statement at 
the beginning of the subroutine, and list all the variables whose values
you want to preserve between calls.

This is all covered in the Fortran 77 standard, BTW.

Jon Bell / Dept. of Physics & Computer Science / Presbyterian College
Clinton SC / jtbell@presby.edu


Newsgroups: comp.lang.fortran
From: john@spectre.unm.edu (John Prentice)
Subject: Re: C versus FORTRAN debate
Date: Sat, 22 Aug 92 20:12:15 GMT
Organization: Dept. of Math & Stat, University of New Mexico, Albuquerque

In article <1992Aug19.143047.18550@ultb.isc.rit.edu> jsvrc@rc.rit.edu (J A Stephen Viggiano) writes:
>In article <py0mz+n@lynx.unm.edu> john@aquarius.unm.edu (John Prentice) writes:
>. . . .
>>Continuing to compare F77 to languages like C is a bit silly.  
>
>As is comparing FORTRAN 90 to languages like C. (Sorry, no ":-)".)

Perhaps you are right, C might not fare so well (Sorry, no ":-)".)
-- 
John K. Prentice                      
Quetzal Computational Associates    
3200 Carlisle N.E., Albuquerque, NM   87110-1664; 505-889-4543
john@spectre.unm.edu -or- jkprent@cs.sandia.gov -or- john@aquarius.unm.edu
From: yucao@sampson.ccsf.caltech.edu (Yu Cao)
Newsgroups: comp.lang.fortran
Subject: NAMELIST simulating routine
Keywords: NAMELIST
Date: 21 Aug 92 04:45:40 GMT
Organization: California Institute of Technology, Pasadena

Has anybody written such a thing that enables you to read NAMELIST formatted
files when the compiler doesn's support it?

Any info is appreciated.

--Yu
Newsgroups: comp.lang.fortran
From: Bruce.Scott@bbs.oit.unc.edu (Bruce Scott)
Subject: how to quit on an NaN result?
Organization: Extended Bulletin Board Service
Date: Sun, 16 Aug 1992 20:08:37 GMT

Hello all,
  I am debugging code which is still in the stage where many NaN results
arise. The problem is that, beyond the waste of time in general,
operations involving these critters are very slow. How can I check for
NaN's and quit when one arises. Does one use
        if (avar .eq. 'NaN') stop
or is this illegal?

Gruss,
Dr Bruce Scott                             The deadliest bullshit is
Max-Planck-Institut fuer Plasmaphysik       odorless and transparent
bds at spl6n1.aug.ipp-garching.mpg.de                 -- W Gibson

--
   The opinions expressed are not necessarily those of the University of
     North Carolina at Chapel Hill, the Campus Office for Information
        Technology, or the Experimental Bulletin Board Service.
           internet:  bbs.oit.unc.edu or 152.2.22.80
Newsgroups: comp.lang.fortran