home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.lang.fortran:2997 comp.lang.c:12229
- Path: sparky!uunet!olivea!hal.com!decwrl!elroy.jpl.nasa.gov!lambda.msfc.nasa.gov!robichau
- From: robichau@lambda.msfc.nasa.gov (Paul Robichaux)
- Newsgroups: comp.lang.fortran,comp.lang.c
- Subject: Moving from FORTRAN to C: supporting or porting?
- Message-ID: <1992Aug12.185859.8931@lambda.msfc.nasa.gov>
- Date: 12 Aug 92 18:58:59 GMT
- Reply-To: robichau@lambda.msfc.nasa.gov
- Organization: New Technology, Inc.
- Lines: 30
-
- The system I'm helping to develop here at Marshall includes a facility for
- letting scientists/principal investigators (our users) build
- C-language computations that ingest spacecraft telemetry, do some type
- of calculations, and do something with the result.
-
- Our system is a workstation & POSIX-based follow-on to the current VAX
- VMS implementation. The current system allows user comps to be written
- (naturally) in FORTRAN.
-
- The problem is this: our requirements document specifically requires
- C, and it also requires grandfathering _all_ capabilities of the
- current system.
-
- We have two options: make all the current users port their stuff once,
- and disallow further use of FORTRAN, or support both languages. Each
- approach has its advantages and disadvantages, not all of which we've
- though of.
-
- I'm looking for {success | horror | war} stories about this sort of
- problem. We _have_ to support both languages, but no one's defined
- what "support" means in this context.
-
- Please reply via posting; replies via e-mail will be summarized.
-
- Thanks,
- -Paul
-
- --
- Paul Robichaux, KD4JZG | I shouldn't bitch / I shouldn't cry
- robichau@lambda.msfc.nasa.gov | I'd start a revolution but I don't have time.
-