HDTenEightyP/NetNews huggingface dataset:
From: jlg@cochiti.lanl.gov (Jim Giles)
Subject: Re: Welcome to HPFF
Keywords: HPFF, High Performance Fortran
Organization: Los Alamos National Laboratory
Date: Fri, 14 Aug 1992 16:34:55 GMT

In article <1992Aug14.092952.11572@ibr.cs.tu-bs.de>, i2041101@rzphy1.rz.tu-bs.de (Paulini) writes:

|> [...]         Compared to other languages (even to cryptic C - Codes)
|> FORTRAN is not recommendable as a programming language at all. It is merely
|> a collection of erratic ideas and lacks a real conception. 
                   ^^^^^^^^^^^^^     ^^^^^^^^^^^^^^^^^^^^^^^

C suffers from both these problems to a VASTLY greater extent than 
Fortran, yet you recommend C.  Given a choice between Fortran and C 
as a starting point for the design of a new language, Fortran would 
be a much better choice.  Yes, Algol 60 (but not Algol 68) might
be a better basis than Fortran (that is long since out of anyone's
hands).

Haskell, Scheme, etc. might perhaps be even better choices for some
markets (but probably not for scientific coding).  Certainly, C would
be at the bottom of the list no matter *what* other languages were 
mentioned.  Fortran is certainly better designed, less erratic, and 
better conceived than C (and C cannot be sufficiently improved without 
making incompatible alterations to the present standard).

Also, this is comp.lang.fortran.  If you don't want to participate,
don't.  In the meantime, if you denounce (with some justification) some
of the characteristics of Fortran, it is inconsistent to recommend a
replacement which suffers the same deficiencies to a much greater extent.

-- 
J. Giles
From: pam@mefos.se (PA Monwall)
Newsgroups: comp.lang.fortran
Subject: Re: Unix ARGC,ARGV in Fortran 77
Date: 18 Aug 92 14:32:59 GMT
Organization: MEFOS, Sweden

Shame PA........
My followup was regarding passing ARGV and ARGV in VAX/FORTRAN!!!!!!!
Not in f77/Ultrix. 
But you can try with the functions iargc and getarg. Maybe they 
exists in f77/Ultrix.

--------
	character*40 string

	narg = iargc()			! Get number of args
	do 100 n=1,narg
	   call getarg(n,string)	! Get arg n in string
	   ...
	   ....
100	continue

--------

----------------------------!------------------------------------------------
    /////// /////// //   // ! PA Monwall               E-mail: pam@mefos.se
   //   // //   // ///////  ! Foundation for Metallurgical Research (MEFOS)
  /////// /////// // / //   ! Box 812, S-951 28 Lulea, Sweden
 //      //   // //   //    ! Tel: +46 920 55640  Home : +46 920 221581
//      //   // //   //     ! Fax: +46 920 55832  Telex: 80482 MEFOS S 
Newsgroups: comp.lang.fortran
From: jaaksi@cs.tut.fi (Jaaksi Ari)
Subject: Fortran subroutine in C main (2)
Organization: Tampere Univ. of Technology, Finland.
Distribution: comp.lang.fortran
Date: Tue, 18 Aug 1992 17:24:06 GMT


Hi!

How to use Fortran subroutines called from C main. Everything
else seems to be OK except when some IO -routines occur in
Fortran subroutines. F.ex. I've got a Fortran module that writes
a file and it works fine when called from Fortran main program. 
When I try to call it from C, I get error messages like

	Error: _IO_Open undefined

	Error: _IO_Write_List_Seq undefined

	*** Error code 2

	Stop.

at the time I try to link my .o files. If I remove all my IO-things
I don't get any error messages and as I said all goes fine! 

Is there any way to handle these problems.

I use Stardent 3000 computer, TitanOS UNIX Release 4.1 and it's 
compilers Fortran 77 (fc) and C (cc).

All kind of info is more than welcome.

Ari Jaaksi
--
From: Peter.Hammond@brunel.ac.uk (Peter D Hammond)
Newsgroups: comp.lang.fortran
Subject: Re: BC-F77 Document in English
Date: 13 Aug 92 15:53:44 GMT
Organization: Brunel University, Uxbridge, UK
X-Newsreader: Tin 1.1 PL3

Hi.
I attempted to post the requested document earlier today, but the message
body came out blank. Sorry to sound thick, but how do I post a file instead
of having to retype the whole thing? I'm using the tin newsreader,
if that is immportant. I suppose it is. It invokes vi to compose messages.

Somebody tell me and I'll try again. I've so far had about 6 requests,
so I suppose there is demand.


-- 
BFN, Pete.

 Dept. Materials Technology | Disclaimer: SERC pay me | You sometimes have to  
 Brunel University          | to report my opinions,  |    listen to
 Uxbridge                   | not for theirs or the   | A lot of useless talk.
 Middx, UB8 3PH, UK.        | the university's.       |         N. Peart. (RUSH)
Newsgroups: comp.lang.fortran
From: fardad@bostech.com (Fardad Farahmand)
Subject: Fortran to C translator
Organization: Boston Technology, Wakefield, MA
Date: Wed, 12 Aug 92 20:48:53 GMT


I need a utility to convert FORTRAN source to C.  I hope to find it
for free, but will pay a small fee if necessary.

If I can't find this anywhere I'll have to learn FORTRAN again and
convert this rather large set of routines by hand.  

Please email me your comment since I don't normaly read this
newsgroup.

Thanks
FF

fardad@bostech.com


Newsgroups: comp.lang.fortran
From: jsvrc@rc.rit.edu (J A Stephen Viggiano)
Subject: Re: how to quit on an NaN result?
Organization: RIT Research Corp
Date: Mon, 17 Aug 1992 15:59:13 GMT

In article <1992Aug16.200837.14024@samba.oit.unc.edu> Bruce.Scott@bbs.oit.unc.edu (Bruce Scott) writes:

> How can I check for NaN's and quit when one arises. Does one use
>        if (avar .eq. 'NaN') stop
>or is this illegal?

The answers are: No, and No, respectively. I tried this a couple of years ago,
and proposely put some NaNs through. (I didn't include the quotes in the
test, though.) The test always failed, because NaNs are unordered, so one
can never equal another. (This might be compiler-dependent, though.)

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.
From: khb@chiba.Eng.Sun.COM (Keith Bierman fpgroup)
Newsgroups: comp.lang.fortran
Subject: Re: how to quit on an NaN result?
Date: 17 Aug 92 19:28:06
Organization: Sun MegaSystems
 <KHB.92Aug16143141@chiba.Eng.Sun.COM> <92230.171200HDK@psuvm.psu.edu>
NNTP-Posting-Host: chiba
In-reply-to: HDK@psuvm.psu.edu's message of 17 Aug 92 21:12:00 GMT



>but most exception (interrupt) handlers would set the intermediate result

No. The default is to fully conform to IEEE 754 which mandates
denormalization. On an IBM S/370 family machine this would, of course,
not be the case.

The observation about cost is well taken. The cost of doing this *can*
be non-trivial. On the TI SuperSPARC chip it is "free" (viz. done in
hw) on the LSI and Cypress SPARC chipsets used in the 4/60|65|75 etc.
family, it is expensive.


--
----------------------------------------------------------------
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: fox@rudolf.nscl.msu.edu (Ron Fox)
Newsgroups: comp.lang.fortran
Subject: Re: BCF77 Document in English
Date: 14 Aug 92 12:04:12 GMT
Reply-To: fox@rudolf.nscl.msu.edu (Ron Fox)
Organization: National Superconducting Cyclotron Lab.

--
  Not to be picky, but exactly where can one get the bcf compiler
itself?
	Thanks,
	Ron
Ron Fox                     | FOX@MSUNSCL.BITNET      | Where the name 
NSCL                        | FOX@RUDOLF.NSCL.MSU.EDU | goes on before
Michigan State University   | MSUHEP::RUDOLF::FOX     | the quality
East Lansing, MI 48824-1321 |                         | goes in.
USA
Newsgroups: comp.lang.fortran
From: schieb@shark.gsfc.nasa.gov (Brian D. Schieber)
Subject: WILDCARD expansion in UNIX FORTRAN
Reply-To: schieb@shark.gsfc.nasa.gov (Brian D. Schieber)
Organization: Oceans & Ice Branch, NASA/GSFC/GSC
Distribution: na
Date: Thu, 13 Aug 1992 12:55:38 GMT

 I'm porting a VAX FORTRAN program to UNIX that uses VAX library
calls to expand a wildcard for filenames into an array of strings.
Is there any such capability for UNIX FORTRAN? Short of doing
a SYSTEM call and running 'find' I don't know how this would be
done.

Suggestions appreciated.

Thanks,


--Brian

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^ Brian D. Schieber            NASA/Goddard Space Flight Center ^
^ schieb@shark.gsfc.nasa.gov   Laboratory for Hydrospheric      ^
^ DECnet: urchin::schieb        Processes                       ^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Newsgroups: comp.lang.fortran,comp.sys.sun.apps
From: pat@jaameri.gsfc.nasa.gov (patrick m. ryan)
Subject: need FORTRAN compiler for SS10
Reply-To: pat@jaameri.gsfc.nasa.gov (patrick m. ryan)
Organization: Oceans & Ice Branch, NASA/GSFC/STX
Distribution: na
Date: Tue, 18 Aug 1992 12:36:41 GMT


	I need some recommendations for a 3rd party FORTRAN
compiler for a SPARC 10.  Sun wants $1,500 for their FORTRAN
which is a little beyond our budget right now.  As I understand
it, GNU FORTRAN is still in the larva stage so I can't use that
yet.
	If you know of a good FORTRAN compiler for Sun, please
send me email.  I'll summarize any answers I get.

thanks,
pat

--
                                                             patrick m. ryan
     nasa / goddard space flight center / oceans and ice branch / hughes stx
                     pat@jaameri.gsfc.nasa.gov / zmpmr@charney.gsfc.nasa.gov
From: lapoint@adios.brl.mil (Claude LaPointe )
Newsgroups: comp.lang.fortran
Subject: RE:  STORAGE OF ARRAYS IN FORTRAN
Date: 13 Aug 92 13:49:43 GMT


jlg@cochiti.lanl.gov (Jim Giles) writes:

  > In article <976@aos.brl.mil>, lapoint@adios.brl.mil (Claude LaPointe ) writes:
  > |> [...]
  > |> The idea that the 1st subscript corresponds to columns, the second to
  > |> rows, the 3rd to planes, the 4th... OOPS! no more analogies,
  > |> is merely conventional and has nothing to do with storage.
  > |>
  > |> Most FORTRAN types accept the convention that the 1st runs down
  > |> the column; the 2nd, across the row, ....
  >
  > I use the convention that the first index is the column number, the second
  > the row number etc. simply because it simplifies I/O requests in Fortran:
  >
  >       REAL A(2,3)
  >       ...
  >       write(*,'(2F10.5)') A
  >       ...
  >
  > This code fragment will write out the values of A's components in the
  > order:
  >
  >       A(1,1)  A(2,1)
  >       A(1,2)  A(2,2)
  >       A(1,3)  A(2,3)
  >
  > Any other order of I/O would require implied do-loops or some other
  > looping mechanism.  Note, this convention does not hamper users in C, or
  > Pascal, etc. because they don't have built-in syntax for reading/writing
  > whole arrays anyway - so you must always use loops in those languages.
  > Of course, if your language uses row-major, pragmatic considerations
  > may force row-major I/O as well (at least on large arrays) because of
  > the cost of striding.


Most FORTRAN people make the other interpretation, that the 1st subscript
is the row number and runs down the column. This is the choice, for instance,
of Balfour and Marwick's textbook, and even of the Cray FORTRAN reference
manual, volume 1.


Nevertheless, jlg's choice and rational make sense. Note that he interprets
the 1st subscript as the column number, that is, it runs across the row.


My only point was, and is, that the storage sequence, being linear,
does not enforce or even prefer either view. Even concerns of stride
in various machines, although important, are independent of the picture
one uses to interpret what each subscript does. In standard FORTRAN, at
least, the storage sequence merely runs out the 1st subscript before
incrementing the 2nd one, as follows:

   linear_subscript = (value_of_2nd_subscript-1) * size_of_1st_dimension
                      + value_of_1st_subscript

Clearly, my expression is not the most general one, even for only 2
dimensions. It assumes something of the form

   DIMENSION ARRAY(2,3)

rather than of form

   DIMENSION ARRAY(-17:-16,-1:1)

which would result in "offset" terms in the linear_subscript expression.
From: Peter.Hammond@brunel.ac.uk (Peter D Hammond)
Newsgroups: comp.lang.fortran
Subject: Source of BCF77
Date: 14 Aug 92 10:01:37 GMT
Organization: Brunel University, Uxbridge, UK
X-Newsreader: Tin 1.1 PL3

When I say source, I mean `place you can get it', not `source code'.
In response to E-mail requests, I got BCF77 from Cica, anonymous FTP
ftp.cica.indiana.edu.
Also it is on rusmv1.rus.uni-stuttgart.de, but that mahcine takes about
3 hours at least to transfer it, and when I got it the zip wouldn't 
expand properly. I belive it is on several other sites as well.

All this was posted here a few weeks/months back, which is where I heard
about it, but I was asked, so don't flame me for wasted bandwidth.

And by the way, that was not intended as a flame to those who asked me
to post this info.


-- 
BFN, Pete.

 Dept. Materials Technology | Disclaimer: SERC pay me | You sometimes have to  
 Brunel University          | to report my opinions,  |    listen to
 Uxbridge                   | not for theirs or the   | A lot of useless talk.
 Middx, UB8 3PH, UK.        | the university's.       |         N. Peart. (RUSH)
From: jlg@cochiti.lanl.gov (Jim Giles)
Newsgroups: comp.lang.fortran,slac.lang.fortran
Subject: Re: What is the name of the latest Fortran stan
Date: 14 Aug 92 18:05:50 GMT
Organization: Los Alamos National Laboratory

Try ISO/IEC 1539:1991(E).  This is the completed ISO standard. 

-- 
J. Giles
From: Peter.Hammond@brunel.ac.uk (Peter D Hammond)
Newsgroups: comp.lang.fortran
Subject: Re: What extensions do you use?
Date: 13 Aug 92 13:32:43 GMT
Organization: Brunel University, Uxbridge, UK
X-Newsreader: Tin 1.1 PL3

Hi.
I am lucky (?) enough to only program on one platform, Sun 4, so using
extensions is no problem. I dont sell my code, so if anyone nicks it
then trying to port it is their problem!

I find the following very useful:
Long (ie meaningfull) identifiers
Trailing comments (eg
	if ( a .ne. b ) then  ! If mismatched, sort it out...
and various of the Sun library functions, which I suppose could be called
language extensions. In addition, I often use unlabelled do loops, because
I think they are tidyer than all those continue statements.

Just my 2p worth.
As programmers go, I make a pretty good materials scientist...

-- 
BFN, Pete.

 Dept. Materials Technology | Disclaimer: SERC pay me | You sometimes have to  
 Brunel University          | to report my opinions,  |    listen to
 Uxbridge                   | not for theirs or the   | A lot of useless talk.
 Middx, UB8 3PH, UK.        | the university's.       |         N. Peart. (RUSH)
Newsgroups: comp.lang.fortran
From: langer@aero.org (John V. Langer)
Subject: Re: What extensions do you use?
Organization: The Aerospace Corporation, El Segundo, CA
Date: Fri, 14 Aug 1992 10:12:08 GMT

In article <1992Aug13.004448.4409@ccu1.aukuni.ac.nz> ecmtwhk@ccu1.aukuni.ac.nz (Thomas Koenig) writes:
>What extensions do you usually use when programming FORTRAN? I try to
>restrict myself to two: Use of INCLUDE statements, without which COMMON
>blocks and PARAMETER statements would be almost impossible, and
>IMPLICIT none. Altough the temptation to use identifiers longer than 6
>letters can be overwhelming, I usually don't because one system I work
>on does not support them; same goes for use of lowercase letters.
>
>How about you?

Hollerith data.  You know, the way we used to pack "character" information
into integer or floatiing-point variables before the ANSI-77 standard gave
us the CHARACTER data type.  Before you dismiss me as totally silly, let
me explain:

       (1)  I use a *lot* of large, complex, "dusty-deck" software
            the derives from the 60's and uses this "data type" in
            many critical ways.  You can't take it all out, it's 
            like a deep-seated cancer.

       (2)  *Every* Fortran compiler I have ever tried (DOS-based, VMS,
            Mips/SPARC/68000 Unix Workstation-based, old and new CDC-
            based, CRAY COS/UNICOS-based, IBM/MVS-based) has supported
            this feature.

            I hope and pray Craig Burley will include it in his new
            compiler.

In every other respect I stay strictly to the standard -- even limiting
my character set to capital letters.  I agree that an "include" function
is indispensible, but I satify that need with a pre-compiler pre-processor
(a short home-grown program similar to the C preprocessor "cpp").  I don't
use IMPLICIT NONE, but I always turn on any compiler options providing
the same functionality and, if there are no such options, the wonderful
"ftnchek" utility will find the improprieties.

-- 
===============================================================================
| langer@aerospace.aero.org  |  jvl@mickey.aero.org  |  langer@130.221.192.10 |
===============================================================================
Newsgroups: comp.lang.fortran
From: Patrick F. McGehearty <patrick@convex.COM>
Subject: Re: summary (was Fortran 90:  Pointers to Functions?)
Originator: patrick@mozart.convex.com
Date: Tue, 18 Aug 1992 18:12:40 GMT
Reply-To: patrick@convex.COM (Patrick F. McGehearty)
Organization: Engineering, CONVEX Computer Corp., Richardson, Tx., USA
X-Disclaimer: This message was written by a user at CONVEX Computer
              Corp. The opinions expressed are those of the user and
              not necessarily those of CONVEX.

In article <16q6bdINNpqh@darkstar.UCSC.EDU> sla@fast.ucsc.edu (Steve Allen) writes:
>This is the final summary of all gleaned wisdom on the topic of
>Pointers to Functions in Fortran 90.
...
>
>Overall this subject has provoked remarkably little response, and I'm
>gonna shut up and keep working on the (Fortran 77) code for my thesis.
...
There is a way to get the desired functionality using computed goto's.
Determine every possible function that might be assigned to the pointer.
Write a function which is called with the same arguments plus an index.
Store the index in an integer instead of the function in a pointer.

I.e.: Assume F1,F2,...,FN might be called.  F? has arguments ARG1,ARG2.
Then:

	FUNCTION INDIRECTF(INDEX,ARG1,ARG2)
	IF (INDEX .LT. 0) GO TO 9999
C Assume MAXINDEX set in an appropriate PARAMETER statement
	IF (INDEX .GT. MAXINDEX) GO TO 9999
	GO TO (10,20,...,NN)INDEX
10	INDIRECTF = F1(ARG1,ARG2)
	RETURN
20	INDIRECTF = F2(ARG1,ARG2)
	RETURN
	...
NN	INDIRECTF = FN(ARG1,ARG2)
	RETURN
9999	... print appropriate error message ...
	STOP
	END

It looks ugly, and the initial setup is tedious, especially compared to
using C function pointers.  It also adds the overhead of an additional
subroutine call.  It has the advantage of forcing all possible callee's to
be identified for later maintainers.  Additional functions can be added
easily, only requiring two lines for the function call, extention of the
computed GOTO, and a change to MAXINDEX.   A file documenting the
correspondence between index and the function should also be maintained.

I did something similar using ASSIGNED GOTO's on a CDC6600 many years ago. :-)
While it worked fine for my application, it was not necessarily portable.
Only later did I learn enough about standards and portability to realize
that in many implementations ASSIGNED GOTO's don't work across routine
boundaries.
Newsgroups: comp.lang.fortran
From: hybl@umbc4.umbc.edu (Dr. Albert Hybl (UMAB-BIOPHYS))
Subject: Re: Fortran 90:  Pointers to Functions?
Keywords: missing feature?
Organization: University of Maryland Baltimore Campus, Academic Computing Services
Date: Wed, 12 Aug 1992 12:42:12 GMT

In article <1693l7INNn4o@darkstar.UCSC.EDU> sla@fast.ucsc.edu (Steve Allen) writes:
>In article <166htnINNhvn@darkstar.UCSC.EDU> sla@fast.ucsc.edu I wrote:
>>[paraphrased and condensed]
>>Does Fortran 90 have something which matches the concept and
>>functionality of C's "pointer to a function" in the manner of
>>       int (*func)();
>Is there some other (reasonably elegant) method for getting this
>kind of functionality in Fortran 90?
>Steve Allen (sla@helios.ucsc.edu)

Good, you could spend 20 years trying to get it into F77/F90/F2001
or you could have asked your vendor to put it into their compiler
as an extension, instead you are asking the fortran community to
help find a solution.  It is an ideal project for experimention.

Several F77 features were added because they existed in widely used
preprocessors.  Perhaps some of your friends at NOAO working
with IRAF could put this feature into their xpp preprocessor
or perhaps someone could put it into GNU F90 when one becomes
available.  Perhaps it is time to allow C-language inclusions into
fortran; that could "fix" many problems.

Cheers,
Albert Hybl (hybl@umbc3.umbc.edu)
From: sla@fast.ucsc.edu (Steve Allen)
Newsgroups: comp.lang.fortran
Subject: summary (was Fortran 90:  Pointers to Functions?)
Date: 18 Aug 1992 06:46:05 GMT
Organization: UCO/Lick Observatory
NNTP-Posting-Host: fast.ucsc.edu
Summary: like I said

This is the final summary of all gleaned wisdom on the topic of
Pointers to Functions in Fortran 90.

Fortran 90 does not have anything which matches the concept of pointers
to functions as in the C language.  It does have the ability to pass
single functions into another function using the EXTERNAL declaration;
this is the same as in the Fortran 77 syntax.

This means that it is not possible to have "arrays of functions" or
"structures containing an element which is a function" as in C.

It is also not clear just what the meaning of a "pointer to a function"
would be on some kinds of multi-processor systems.

klassen@sol.UVic.CA (Melvin Klassen) points out that with some Fortran 77s it
is possible to fake this functionality by making use of argument mismatch.
This might be accomplished by passing a function into some other routine
using EXTERNAL and withing the receiving routine declaring that dummy
argument to be an INTEGER which stores the received value.  With some
Fortran compilers this may require a non-Fortran intermediary because
the EXTERNAL may be passed "by value" rather than "by reference".

It is not clear whether this kind of cheating will actually work with
the new "vector-valued functions" of Fortran 90.

Overall this subject has provoked remarkably little response, and I'm
gonna shut up and keep working on the (Fortran 77) code for my thesis.
_______________________________________________________________________________
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.
Xref: sparky comp.lang.fortran:3062 sci.math.stat:1675
From: dale@imsl.UUCP (Dale Neaderhouse)
Newsgroups: comp.lang.fortran,sci.math.stat
Subject: IMSL/random number generation
Keywords: random number generation, multiplicative congruential generators
Date: 17 Aug 92 15:59:23 GMT
Organization: IMSL, Inc., Houston

In article <1992Aug14.140728.22892@porthos.cc.bellcore.com>  
chh2@rigel.uucp (22352-halevi) writes:
> So, anyone out there know what ggubs is

GGUBS was renamed to RNUN in 1987 version 1.0 of the IMSL Stat/Library
for Fortran.

In the 1.0 and 1.1 versions, RNUN used one of six algorithms for generating 
random numbers.  In version 2.0, a seventh was added in September 1991.

1. Congruential, with multiplier 16807 is used.
2. Congruential, with multiplier 16807 is used with shuffling.
3. Congruential, with multiplier 397204094 is used.
4. Congruential, with multiplier 397204094 is used with shuffling.
5. Congruential, with multiplier 950706376 is used.
6. Congruential, with multiplier 950706376 is used with shuffling.
7. Generalized Feedback Shift Register, with the recursion 
       X_t  = X_(t-1563) (+) X_(t-96) is used.

GGUBS used the first algorithm. Plese study the literature in this
field to know what tests pass for the different algorithms and which
tests fail.

I hope this helps.

Dale

Have a good day!
 
Dale L. Neaderhouser          dale@imsl3.imsl.com   FAX: 713-242-9799
Senior Software Engineer      uunet!imsl!dale      IMSL: 713-242-6776
Post Sales Technical Support: 800-324-4675        Sales: 800-222-4675