Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.os.vms    |    DEC's VAX* line of computers & VMS.    |    264,096 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 262,440 of 264,096    |
|    =?UTF-8?Q?Arne_Vajh=C3=B8j?= to Dave Froble    |
|    Re: Local Versus Global Command Options    |
|    22 Feb 25 15:10:30    |
      From: arne@vajhoej.dk              On 2/22/2025 11:40 AM, Dave Froble wrote:       > On 2/22/2025 9:29 AM, Arne Vajhøj wrote:       >> On 2/22/2025 8:53 AM, Arne Vajhøj wrote:       >>> On 2/22/2025 12:53 AM, Dave Froble wrote:       >>>> On 2/21/2025 11:15 PM, Arne Vajhøj wrote:       >>>>> There are some ways to start a process with a DCL command       >>>>> (and therefore DCL mapped).       >>>>>       >>>>> There are some ways to start a process without specifying a DCL       >>>>> command and still getting a process with DCL mapped.       >>>>>       >>>>> There are some ways to start a process without DCL mapped.       >>>>       >>>> Now I'm confused. Were we discussing starting an image in an existing       >>>> process, or starting a new process?       >>>       >>> Starting a new process.       >>>       >>> Because it is about a program running another program. And that       >>> indicate starting a new process.       >>       >> Unless LIB$DO_COMMAND which is special.       >       > I recall that that starts a subprocess. If I remember correctly. Which       > would be a new process.              LIB$SPAWN starts a new subprocess.              LIB$DO_COMMAND exits current image and execute the command       within the same process.              Arne              --- SoupGate-DOS v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca