home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.fortran
- Path: sparky!uunet!nih-csl!helix.nih.gov!rvenable
- From: rvenable@helix.nih.gov (Richard M. Venable)
- Subject: Re: How to get command line arguments from unix with FORTRAN?
- Message-ID: <1993Jan26.200311@helix.nih.gov>
- Sender: postman@alw.nih.gov (AMDS Postmaster)
- Reply-To: rvenable@helix.nih.gov (Richard M. Venable)
- Organization: National Institutes of Health
- References: <1993Jan25.214008.10580@leland.Stanford.EDU> <1k1palINNao2@morrow.stanford.edu> <PMURPHY.93Jan26121847@orangutan.cv.nrao.edu>
- Date: Wed, 27 Jan 1993 01:03:11 GMT
- Lines: 24
-
- In article <PMURPHY.93Jan26121847@orangutan.cv.nrao.edu>,
- pmurphy@nrao.edu (Pat Murphy) writes:
- |> A brief experiment with telnet shows that his posting machine is not
- a
- |> Sun: "ULTRIX V4.2A (Rev. 47)". My f77 info for Ultrix (4.0),
- |> fortunately shows getarg identical to the above. However I know
- that
- |> for other flavors of unix it is different. For example, HP-UX uses
- a
- |> function IGETARG with three arguments.
-
- Ah, but you can still use GETARG under HP-UX; it's just that IGETARG
- provides info on the length of the string returned, while GETARG does
- not. Also, a compiler directive is required to use GETARG. However,
- I think HP's biggest sin here is that CALL GETARG(1,string) returns
- the program name, where most other implementations consider that to be
- argument 0 (zero) and not 1 (one).
-
- -----------------------------------------------------------------
- Rick Venable | "Eschew
- FDA/CBER Biophysics Lab | Obfuscation"
- rvenable@helix.nih.gov | -- the Phantom Nerd
- -----------------------------------------------------------------
-
-