Newsgroups: comp.parallel.pvm
Path: ukc!uknet!pipex!howland.reston.ans.net!europa.eng.gtefsd.com!gatech!darwin.sura.net!rouge!sxb
From: sxb@swamp.cacs.usl.edu (Sriram Kumar)
Subject: Porting from PVM 2.x to PVM 3.x
Message-ID: <1994Mar1.210325.28315@usl.edu>
Keywords: porting, automation, PVM 2.x->PVM 3.x
Sender: anon@usl.edu (Anonymous NNTP Posting)
Organization: Univ. of Southwestern Louisiana
X-Newsreader: TIN [version 1.2 PL1]
Date: Tue, 1 Mar 1994 21:03:25 GMT
Lines: 21


Dear Netters,

I have a question regarding porting the programs written for 
PVM 2.4 to PVM 3.x.

I partially automated the porting using lex (the 3.x manual 
gives details as to how to map the function names). However, 
there are some semantic incompatibilities between 2.4 and 
3.x code (for example the <task, inum> vs <tid>). 

Therefore, to make the converted program work under 3.x, I 
have to edit the new file manually to reflect 3.x conventions. 
So far I have not been able to automate this process.

I welcome your comments on this problem. If anybody has 
automated this porting, please let me know.

Thanks for your help,
Sriram


