"JLE":

[snip]
The code is much more portable in C.
[snip]

I disagree.... where are the equivalent high quality field proven
mathematical
subroutine libraries?

Jeesh... software "fads"...

Just because some computer jockey say it's fashionable
ya'll follow along like sheep to the slaughter!

Shades of Bill Gates crappy bloatware. His empire would have collapsed
long ago if not for us hard working hardware Engineers. It's that
slavish devotion to software "fashion" that we see exhibited in this thred
that created Gates evil empire in the first place!

What do people see in "C"? :-)

[snip]
He has done the amateur community a real service and is to be commended.
Your inane comments to the contrary.
[snip]

I agree the OP has done some heavy lifting, but done us service!

Ummm. Nahhh!

How many bugs has he introduced in a perfectly fine program?

Compared to C, modern Fortran is much more suitable in all aspects such as
precision, speed and clairity of purpose and understanding in alignment to
the
original mathematics. Fortran has "native" support for complex and
vector/matrix
arithmetic all advantages over C when applied to large mathematical
manipulations
involving complex arithmetic and multi-dimensional complex arrays such as in
NEC.

C is a system programming language, not a mathematical programming language!

A skilled tradesman uses the right tool for the right job.

There are jobs for which C is quite suitable, but large mathematical
operations
like NEC is not one of them! C seems simple, but hey... where are all of
those
extensive widely proven highly accurate math subroutine libraries for C!
Ugh!

The problem with these danged "so-called" computer scientists is that they
all want to make every tool a religion and don't know which tool to use
for which job.

Why use a sledge hammer to open a walnut? Or a saw to slice bread?

Hey... get real, we Hardware Engineers never let "slide rule scientists"
tell us how
to compute, why now then do we let these so-called "computer scientists"
tell us we are using the wrong tools, when we know better!

Wake up... Don't fall for their stupid con games! They'l soon all be
replaced
by GUI visual code generating automatons anyway!

Converting NEC to Fortran 90/95 would have made more sense than
converting it to C.

I agree, FORTRAN (66 and 77) are old and showing their age. But that's
not the point! FORTRAN should be updated to Fortran, not to C!

Modern Fortran supports all of the old FORTRAN code, and modern concepts
suporting GOTO-less efficient software engineering friendly control
structures.

There is no portability problem, Fortran 90/95 is a very modern language,
with all
of the "modern" structures one expects but without any of the downsides that
non-mathematical languages such as C exhibit when pitted against tough
mathematical
operations.

Fortran 90/95 also has widely available very fast proven optimizing
compilers, some
of them are even free.

Long live Fortran...

--
Peter K1PO
Indialantic By-the-Sea, FL




"Peter O. Brackett" wrote in message
ink.net...
From Fortran to C, what a waste of coding time... and how many errors
were introduced in the translation? Heh, heh. :-)

Many would feel... What a crime?

What's wrong with perfectly good Fortran?

BTW... there's nothing wrong with "GOTO"s that aren't readily fixed with
simple matching "COMEFROM" statements!

Rest in Peace E. Djkystra!

;-)

--
Peter K1PO
Indialantic By-the-Sea, FL.