Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.lang.fortran    |    Putting John Backus on a giant pedestal    |    5,127 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 4,643 of 5,127    |
|    Steven G. Kargl to Lawrence D'Oliveiro    |
|    Re: =?iso-8859-13?B?tEltYWdloSA9ILRQcm9j    |
|    26 Feb 24 01:04:20    |
      From: sgk@REMOVEtroutmask.apl.washington.edu              On Mon, 26 Feb 2024 00:21:01 +0000, Lawrence D'Oliveiro wrote:              > Here’s another bit of terminology the Fortran spec seemed to feel the       > need to invent for itself: talking about “images” to refer to running       > instances of a program. I figured this either meant “thread” or       > “process”, but a clue appears in the 2018 spec, section 11.4, “STOP and       > ERROR STOP statements”:       >       > When an image is terminated by a STOP or ERROR STOP statement, its       > stop code, if any, is made available in a processor-dependent       > manner. If the stop-code is an integer, it is recommended that the       > value be used as the process exit status, if the processor supports       > that concept.       >       > So an image “terminates”, and returns a process “exit status”; this       must       > mean that an “image” is equivalent to a “process”.              Section 3 of the Fortran standard from 2018 defines       the meaning of technical terms. You'll find              3.80       Image       instance of a Fortran program              An 'instance of a Fortran program' could be a grad student       in an office executing her advisor's Fortran program with       pen and paper.              To get a better understand of 'image' see F2018, 5.3.4 Program       execution.              --       steve              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca