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,b9c9ba98cff47596
X-Google-Attributes: gid103376,public
From: dale@cs.rmit.edu.au (Dale Stanbrough)
Subject: Re: Message passing code
Date: 1999/06/24
Message-ID: <dale-2406991635080001@dale.cs.rmit.edu.au>#1/1
X-Deja-AN: 493259295
Distribution: world
References: <7ksh2u$e1e2@svlss.lmms.lmco.com>
X-Complaints-To: abuse@cs.rmit.edu.au
X-Trace: emu.cs.rmit.edu.au 930206128 4971 144.205.16.58 (24 Jun 1999 06:35:28
 GMT)
Organization: RMIT
NNTP-Posting-Date: 24 Jun 1999 06:35:28 GMT
Newsgroups: comp.lang.ada
Date: 1999-06-24T06:35:28+00:00
List-Id: <comp.lang.ada>

dkristol@see-my.sig wrote:

" Over the years i have worked on a number of projects that have
  implemented various message passing schemes for "unique" hardware.
  They usually had a number of traits in common (ports and channels).
  
  Is there a standard interface for such things, and if so, is there
  source code that will work without modification (i.e. standard Ada)
  in a single program, and only need modification in localized
  places (child packages) to work with specific hardware?"


Glade (the ACT implementation of the Ada distributed systems annex)

and 

MPI (message passing interface). I don't know of any Ada bindings, but
i would guess it is pretty trivial from what i have seen.


(I wonder if the two could be combined...)

Dale