From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,aba62ded60e0d703 X-Google-Attributes: gid103376,public From: tmoran@bix.com (Tom Moran) Subject: Re: Spawning a subprocess and communicating with it. Date: 1998/10/12 Message-ID: <36223ffc.5994614@SantaClara01.news.InterNex.Net>#1/1 X-Deja-AN: 400318914 References: Organization: InterNex Information Services 1-800-595-3333 Newsgroups: comp.lang.ada Date: 1998-10-12T00:00:00+00:00 List-Id: >I want to write an Ada program that can start up another Ada > program as a subprocess, coprocess or whatever is the common Unix > paradigm. (I just need it running as a separate, stand-alone > executable image whose execution need go on no longer than that of > the parent program that initiated it.) When the subprocess is up > and running, I need to trade messages back and forth (character > strings are sufficient) between the two processes. This sounds like you could have your main Ada program start a task which would call the main procedure in the other program, and then they could trade information via a (protected) buffer or something. But other messages in this thread suggest that the 'subprogram' may in fact be running on another machine (in which case as noted the Distributed Annex would be appropriate) but it is already in existence and cannot be changed and does not use the Distributed Annex for its communication. That implies the programs need to talk via the OS. Unless the existing program(s) use some OS communication method that is transparent as to whether one, or more, CPUs are involved, it sure sounds like you are going to have to write some glue code to abstract away the CPU count. So this is really a language independent OS question. Or did I miss something?