Should I convert FORTRAN code to C?

[Tom Thackrey]

In article <8807121629.AA07169 at explorer.dgp.toronto.edu> flaps at dgp.toronto.edu (Alan J Rosenthal) writes:
 >
 >swarbric at tramp.Colorado.EDU (Frank Swarbrick) writes:
 >>Try that sort of thing under MS-DOS, with a _BIG_ matrix -- try
 >>something like:
 >>	int array[200][200];
 >>I've tried this sort of thing with Turbo C, and know someone who checked out
 >>MSC for me.  The compiler choked on it because the array exceeds 64K.  However,
Whomever checked MSC didn't RTFM or (s)he would have used the right model
and it would have compiled correctly

 >GEE, this is not part of the C language.  The purpose of a compiler
 >is to hide, or possibly, in the case of MS-DOS, apologize for, the
 >architecture.  If you declare an object of greater size than 64K,
 >pointers to it should use a different segment register value for
 >accesses to elements 32768 and beyond.
32768 elements??? try 64k bytes.

 >Don't judge the C programming language by a few C compilers (and I use
 >the term `C' loosely).  MS-DOS C compilers seem only to accept a subset
 >of the C language because it allows them to compile certain benchmarks
 >into faster code.
I only use MSC (on the pc) and it is a full implementation and very
close to the 'current' ANSI proposed standard.  It has several extensions
to make it easier to generate efficient code for the 808x and 80x86
cpus.  My problem is trying to port programs written in MSC back to
Unix where the compiler does not support some of the proposed ANSI
features.
-- 
Tom Thackrey tat00 at amdahl.uts.amdahl.com <=> amdahl!tat00

[ My opinions are only my own. ]