| View previous topic :: View next topic |
| Author |
Message |
RS
Joined: 22 Jun 2008
Posts: 22
|
 Posted: Mon Aug 25, 2008 2:56 pm Post subject: CALL GETARG(1,BUFFER) |
 |
|
This statement
CALL GETARG(1,BUFFER)
doesn't seem to be capturing the argument that I am passing to the executable. There are no errors or warnings. Should this not work with FTN95?
Thanks |
|
| Back to top |
|
 |
brucebowler
Guest
|
| Posted: Mon Aug 25, 2008 3:24 pm Post subject: |
|
|
| How is BUFFER defined? |
|
| Back to top |
|
|
PaulLaidler
Site Admin
Joined: 21 Feb 2005
Posts: 8220
Location: Salford, UK
|
| Posted: Mon Aug 25, 2008 6:47 pm Post subject: |
|
|
GETARG is not documented in the help file but is available as...
| Code: |
SUBROUTINE GETARG(NARG,ARG)
C RETURN NARG'TH COMMAND LINE ARGUMENT
INTEGER*4 NARG
CHARACTER*(*) ARG |
The alternative is GET_COMMAND_ARGUMENT. |
|
| Back to top |
|
|
RS
Joined: 22 Jun 2008
Posts: 22
|
| Posted: Tue Aug 26, 2008 3:33 pm Post subject: BUFFER defined as character*150 |
|
|
BUFFER is defined as character*150. The argument does not get read into buffer.
I will research the other option that was mentioned (GET_COMMAND_ARGUMENT). |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
