Re: I/O in PURE and ELEMENTAL procedures in Fortran 2008


"Richard Maine" <nospam@xxxxxxxxxxxxx> wrote in message
news:1hxeeov.194py3s18ghpytN%nospam@xxxxxxxxxxxxxxxx
Wade Ward <invalid@xxxxxxxxxxx> wrote:

"Richard Maine" <nospam@xxxxxxxxxxxxx> wrote in message
news:1hxe5oa.1eqhm0ulymfjeN%nospam@xxxxxxxxxxxxxxxx

read_loop: do
call get_data(args, ok)
if (.not. ok) exit read_loop
... process args ...
end do read_loop

I hate to lower your stats by replying, but I wanted to make sure the
above
source is what I think it is. Is it
a) the fortran analog of how C gets arguments from a caller?
b) the way fortran processes a field?
c) reliable input?
d) non-recursive I/O?
Most of the conversation went straight over my head, which I think you'd
rather expect as I'm looking at pure procedures for the first time carefully
in MR&C. I wanted one of my wild guesses to be true, which I thought I
could bank on with d). It was a) that I was interested in, as I do not know
how fortran does what C does with argv and argc.

It could also be getting data from command-line arguments instead of a
file. That would depend on what get_data did.
I'll pursue this another time.
--
WW


.

Relevant Pages

  • Re: dynamic arrays for reading file 2
    ... problems to deal with before going much farther in Fortran programming. ... dependence of the system intrinsic and the system dependence of the wc ... to speak of the fact that the exit status of wc isn't normally available ... the system command tends to be that of the shell instead of that of the ...
    (comp.lang.fortran)
  • Re: Semi-portable Fortran exit codes?
    ... from Fortran programs despite the lack of help from ... the Fortran standard. ... easy access to by calling the POSIXexit subroutine: ... As far as POSIX, I think much effort could have been saved over the ...
    (comp.lang.fortran)
  • Re: Exit code with Fortran 90
    ... Thanks everyone for the replies, now I know that this behaviour is not part of the Fortran 95 standard, but it is part of the 1003.9-1992 standard and may be not avaialable on each Fortran 95 implementation. ... Sending the stop code to the OS as an exit status is not now part of the Fortran standard. ... Two of the enhancements include displaying the stop code on ERROR_UNIT and using it as the process exit status, if the processor has such a concept. ...
    (comp.lang.fortran)
  • Re: I/O in PURE and ELEMENTAL procedures in Fortran 2008
    ... process args ... ... EXIT statement and just thought you were in an infinite ... I'll not try to debate the reasons. ... the fortran analog of how C gets arguments from a caller? ...
    (comp.lang.fortran)
  • Re: Allowed return codes from SYSTEM call in ifort/linux.
    ... The header provides macros to ... returns the exit status of the child. ... This C interface is no good from Fortran, ...
    (comp.lang.fortran)