From schuh@faf6.arc.nasa.gov Wed Mar 5 21:51:00 1997 Received: from faf6.arc.nasa.gov (faf6.arc.nasa.gov [128.102.162.176]) by dkuug.dk (8.6.12/8.6.12) with ESMTP id VAA25590 for ; Wed, 5 Mar 1997 21:50:58 +0100 Received: by faf6.arc.nasa.gov (8.7.1/1.35) id MAA10654; Wed, 5 Mar 1997 12:50:45 -0800 (PST) Date: Wed, 5 Mar 1997 12:50:45 -0800 (PST) From: schuh@faf6.arc.nasa.gov (Michael Schuh) Message-Id: <199703052050.MAA10654@faf6.arc.nasa.gov> To: schuh@faf6.arc.nasa.gov (Michael Schuh), "Jerrold L. Wagener" , adt10@juno.ccc.amdahl.com Subject: Re: (SC22WG5.1333) Fortran 2000 additions Cc: sc22wg5@dkuug.dk > From <@juts.ccc.amdahl.com:adt10@juno.ccc.amdahl.com> Wed Mar 5 10:22:41 1997 > To: "Jerrold L. Wagener" , > schuh@faf6.arc.nasa.gov (Michael Schuh) > Cc: sc22wg5@dkuug.dk > Subject: Re: (SC22WG5.1333) Fortran 2000 additions > > This "minor enhancement" which allows access to command line arguments > must have slipped by me. I like this feature - should have had it > a long time ago. One of the first assembler programs I ever wrote was > to provide this feature. > > Andrew The nicest part about adding this feature is that this feature would make this part of the code portable. Yes, you can use UNIX library calls to get the command line arguments, but it would be much nicer if it was part of the language and would run on all systems. You might have trouble with environment variables on some machines. This could be implemented so that environment variables are used if they exist on a particular machine and yield an "undefined" result if the machine does not support environment variables. In short, I would like to see both command line arguments and environment variables be made available to the programmer as part of a Fortran standard. Thanks again, Michael